Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff6e43801 in __GI_abort () at abort.c:79
#2 0x00000000005ac952 in jerry_port_fatal ()
#3 0x000000000053beef in jerry_fatal ()
#4 0x00000000004f90d3 in ecma_ref_object ()
#5 0x00000000005042cd in ecma_copy_value ()
#6 0x000000000055cf7c in vm_loop ()
#7 0x000000000055b5f6 in vm_execute ()
#8 0x000000000055b193 in vm_run ()
#9 0x000000000051f650 in ecma_op_function_call_simple ()
#10 0x000000000051f2d6 in ecma_op_function_call ()
#11 0x000000000055b9aa in vm_execute ()
#12 0x000000000055b193 in vm_run ()
#13 0x00000000004f501e in jerry_run ()
#14 0x00000000004f25df in main ()
The text was updated successfully, but these errors were encountered:
Thanks for the report. One comment though. "SIGABRT in jerry_port_fatal" is not the best way to describe this issue as jerry_port_fatal and jerry_fatal are simply the internal error handling routines of the engine. That is, the error is actually reported by ecma_ref_object. And SIGABRT is only how jerry_port_fatal terminates the engine in case of an internal error. To get more descriptive error messages, you should add --logging=on to your build options.
Plus, if you put the backtrace in a fenced code block (triple backticks) then the stack frames (e.g., #14) will not be incorrectly linked to past issues or PRs.
The same goes to the test case. Guarding it as a code block will prevent the Markdown engine to re-style __proto__ as proto.
Plus, if you put the backtrace in a fenced code block (triple backticks) then the stack frames (e.g., #14) will not be incorrectly linked to past issues or PRs.
The same goes to the test case. Guarding it as a code block will prevent the Markdown engine to re-style __proto__ as proto.
JerryScript revision
c09c2c5
Build platform
Ubuntu 18.04 LTS
Build steps
python tools/build.py --profile=es2015-subset --lto=off --error-messages=on --strip=off --compile-flag=-fsanitize=address
Test case
Execution steps
build/bin/jerry testcase.js
Output
Program received signal SIGABRT, Aborted.
Backtrace
Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
(gdb) bt
The text was updated successfully, but these errors were encountered: