fix: null array indexing in CTracer_handle_return #1843
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.
Fixes #1835
CTracer_set_pdata_stack
can initializeself.pdata_stack
to an empty stack where->stack
isNULL
and->deph
is -1.Move index into
->stack
into->depth>=0
check to avoid indexing intoNULL
array.This issue was found running UndefinedBehaviourSanitizer. It's reproducible in regular test runs, e.g.
python3 -m tox -e py311
. Addingif (self->pdata_stack->stack == NULL) { fprint(...) }
before the moved line shows the issue in several test cases.The contributing guide mentions ever fix should include tests. I'd be happy to add some, but I'm not quite sure how to do that here. Do you have a preference/advice?