| commit | 5033ea73bb01061feb09b3216c74619e1fbefdeb | [log] [tgz] |
|---|---|---|
| author | Jacob Lalonde <jalalonde@fb.com> | Thu Oct 17 15:26:05 2024 -0700 |
| committer | GitHub <noreply@github.com> | Thu Oct 17 15:26:05 2024 -0700 |
| tree | 20f2f53f8173825b9b2bc130ff25bb5b82dcc483 | |
| parent | 8c62bf54df76e37d0978f4901c6be6554e978b53 [diff] |
[LLDB][Minidump] Add breakpoint stop reasons to the minidump. (#108448) Recently my coworker @jeffreytan81 pointed out that Minidumps don't show breakpoints when collected. This was prior blocked because Minidumps could only contain 1 exception, now that we support N signals/sections we can save all the threads stopped on breakpoints.
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.