Skip to content

Conversation

@DanielBallaSZTE
Copy link

Make sure to ignore static snapshots when sending backtrace information to the debugger.
The JMEM_SET_NON_NULL_POINTER macro requires the frame context's bytecode_header_p pointer to be a heap pointer, but due to the static snapshot it might not be, causing an assertion failure.

This PR is identical to #2608 which I sadly couldn't reopen.
Test environment is not added yet, however this one might be a blocker as well since our VSCode extension uses backtrace and total frame count requests.

JerryScript-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu

Make sure to ignore static snapshots when sending backtrace information to the debugger.
The `JMEM_SET_NON_NULL_POINTER` macro requires the frame context's `bytecode_header_p` pointer to be a heap pointer, but due to the static snapshot it might not be, causing an assertion failure.

JerryScript-DCO-1.0-Signed-off-by: Daniel Balla dballa@inf.u-szeged.hu
@DanielBallaSZTE
Copy link
Author

CC @akosthekiss

Copy link
Contributor

@LaszloLango LaszloLango left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@akosthekiss akosthekiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants