diff options
| author | Javier Lopez-Gomez <javier.lopez.gomez@proton.me> | 2025-05-21 06:29:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-21 05:29:41 +0100 |
| commit | 211ee04a616b0071adefe57015daf5702b0a09b4 (patch) | |
| tree | b0f5a8f23a82b488791c22f69083d0b6afe37538 /llvm/lib/CodeGen/StackMaps.cpp | |
| parent | 9a553d3766aacb69e884823da92dedff264e3f0f (diff) | |
| download | llvm-211ee04a616b0071adefe57015daf5702b0a09b4.zip llvm-211ee04a616b0071adefe57015daf5702b0a09b4.tar.gz llvm-211ee04a616b0071adefe57015daf5702b0a09b4.tar.bz2 | |
[llvm-debuginfo-analyzer] Fix a couple of unhandled DWARF situations leading to a crash (#137221)
This pull request fixes a couple of unhandled situations in DWARF input
leading to a crash. Specifically,
- If the DWARF input contains a declaration of a C variadic function
(where `...` translates to `DW_TAG_unspecified_parameters`), which is
then followed by a definition, `llvm_unreachable()` is hit in
`LVScope::addMissingElements()`. This is only visible in Debug builds.
- Parsing of instructions in `LVBinaryReader::createInstructions()` does
not check whether `Offset` lies within the `Bytes` ArrayRef. A specially
crafted DWARF input can lead to this condition.
Diffstat (limited to 'llvm/lib/CodeGen/StackMaps.cpp')
0 files changed, 0 insertions, 0 deletions