[DWARFVerifier] Fix infinite loop in verifyDebugInfoCallSite (#186413) When attempting to find the callsite for a DwarfDie to see if it was valid or not, there was a while loop that incorrectly attempted to walk up the Die parent hierarch. It set `curr` to parent, but then `curr` was set to same original parent instead of curr.getParent(). This caused infinite recursion on validation of some kernel binaries by llvm-dwarfdump where DW_TAG_call_site was nested inside a DW_TAG_lexical_block (or any non-subprogram, non-inlined_subroutine tag). Fix by changing Die.getParent() to Curr.getParent() so the loop correctly walks up the DIE tree. Add a new test that validates this scenario. Without this change, that test hangs rather than succeeding.
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.