[all-commits] [llvm/llvm-project] 211ee0: [llvm-debuginfo-analyzer] Fix a couple of unhandle...

[Javier Lopez-Gomez via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 211ee04a616b0071adefe57015daf5702b0a09b4
      https://github.com/llvm/llvm-project/commit/211ee04a616b0071adefe57015daf5702b0a09b4
  Author: Javier Lopez-Gomez <javier.lopez.gomez at proton.me>
  Date:   2025-05-21 (Wed, 21 May 2025)

  Changed paths:
    M llvm/lib/DebugInfo/LogicalView/Core/LVScope.cpp
    M llvm/lib/DebugInfo/LogicalView/Readers/LVBinaryReader.cpp
    M llvm/unittests/DebugInfo/LogicalView/DWARFReaderTest.cpp
    A llvm/unittests/DebugInfo/LogicalView/Inputs/test-dwarf-clang-unspec-params.elf

  Log Message:
  -----------
  [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.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications