[LLDB] Improve the logging output from InstrumentationRuntimeBoundsSafety plugin (#175082) This change makes several improvements: * Adds some additional logging in the `InstrumentationBoundsSafetyStopInfo` constructor. In particular logging is now emitted along the success path so we can see what the plugin computed. * `ComputeStopReasonAndSuggestedStackFrame` now logs if the debug info vs no debug info path is taken. * `CheckIfRuntimeIsValid` now prints the correct module path. Previously it always printed `<unknown module>`. * `Deactivate` now prints the breakpoint number correctly. Previously this would try to print signed breakpoints IDs as unsigned. This problem was observable because internal breakpoints use negative breakpoint IDs. rdar://167797706
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.