Fix watchpoint segfault when using debug interpreter without server #1806
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.
Summary
In a previous PR I had introduced memory watchpoint support. This adds two linked lists containing watchpoint locations that are checked on variable reads/writes. However, there is an edge-case where one could be using the
WASM_ENABLE_DEBUG_INTERP
, but not within a debugging instance.In this, the interpreter attempts to read the debugging instance lists which are not initialised. This results in a segmentation fault in
bh_list_first_elem
This change checks whether the interpreter is running within a debugging instance. If not, it assigns the list pointers to null and
bh_list_first_elem
handles this gracefully