-
Notifications
You must be signed in to change notification settings - Fork 438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assertion 'jerry_value_is_function(jonuncaughtexception)' failed in iotjs_uncaught_exception #1349
Labels
Comments
2 tasks
DanielBallaSZTE
pushed a commit
to DanielBallaSZTE/iotjs
that referenced
this issue
Feb 16, 2018
There's a special case where if an uncaughtException is thrown, and later a callback function is evaluated it would throw another one. The correct behaviour for this would be terminating the engine at the first one, and throwing the error. This patch fixes jerryscript-project#1349 IoT.js-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu
DanielBallaSZTE
pushed a commit
to DanielBallaSZTE/iotjs
that referenced
this issue
Feb 16, 2018
There's a special case where if an uncaughtException is thrown, and later a callback function is evaluated it would throw another one. The correct behaviour for this would be terminating the engine at the first one, and throwing the error. This patch fixes jerryscript-project#1349 IoT.js-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu
DanielBallaSZTE
pushed a commit
to DanielBallaSZTE/iotjs
that referenced
this issue
Feb 19, 2018
There's a special case where if an uncaughtException is thrown, and later a callback function is evaluated it would throw another one. The correct behaviour for this would be terminating the engine at the first one, and throwing the error. This patch fixes jerryscript-project#1349 IoT.js-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu
DanielBallaSZTE
pushed a commit
to DanielBallaSZTE/iotjs
that referenced
this issue
Feb 19, 2018
There's a special case where if an uncaughtException is thrown, and later a callback function is evaluated it would throw another one. The correct behaviour for this would be terminating the engine at the first one, and throwing the error. This patch fixes jerryscript-project#1349 IoT.js-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu
DanielBallaSZTE
pushed a commit
to DanielBallaSZTE/iotjs
that referenced
this issue
Feb 19, 2018
There's a special case where if an uncaughtException is thrown, and later a callback function is evaluated it would throw another one. The correct behaviour for this would be terminating the engine at the first one, and throwing the error. This patch fixes jerryscript-project#1349 IoT.js-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu
DanielBallaSZTE
pushed a commit
to DanielBallaSZTE/iotjs
that referenced
this issue
Feb 19, 2018
There's a special case where if an uncaughtException is thrown, and later a callback function is evaluated it would throw another one. The correct behaviour for this would be terminating the engine at the first one, and throwing the error. This patch fixes jerryscript-project#1349 IoT.js-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu
yichoi
pushed a commit
that referenced
this issue
Feb 20, 2018
There's a special case where if an uncaughtException is thrown, and later a callback function is evaluated it would throw another one. The correct behaviour for this would be terminating the engine at the first one, and throwing the error. This patch fixes #1349 IoT.js-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IoT.js version:
OS:
Test case:
Backtrace:
Found by Fuzzinator with grammarinator
The text was updated successfully, but these errors were encountered: