Fix table indexing in dwarf_search_unwind_table
#308
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.
table_len
is used as an index intotable
, assuming it represents the number of entries. However, it is defined as the number of entries multiplied bysizeof(unw_word_t)
. This is accounted for in other places that usetable_len
, e.g. inlookup
, which divides out the size ofunw_word_t
, but the indexing expression usestable_len
directly. So whentable
has say 2 entries, we're actually looking at index 15 rather than 1 in the comparison. This can cause the conditional to erroneously evaluate to true, allowing the following line to segfault.This was observed with JIT compiled code from Julia with LLVM on FreeBSD. It manifested as JuliaLang/julia#41943. Unfortunately we weren't able to come up with a minimal reproducer, as it happened seemingly sporadically in the Julia tests.
cc @vtjnash