Fix possible failure in backtrace info #2643
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make sure to ignore static snapshots when sending backtrace information to the debugger.
The
JMEM_SET_NON_NULL_POINTERmacro requires the frame context'sbytecode_header_ppointer 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