commit | 232525f06942adb3b9977632e38dcd5f08c0642d | [log] [tgz] |
---|---|---|
author | Felipe de Azevedo Piovezan <fpiovezan@apple.com> | Fri Apr 04 10:05:44 2025 -0700 |
committer | GitHub <noreply@github.com> | Fri Apr 04 10:05:44 2025 -0700 |
tree | 4f4feb49a15c209213fad93b2aef64fde544ebbf | |
parent | 5942f0269e62021620e871bfe2e671f4f0f2d932 [diff] |
[lldb] Clear thread-creation breakpoints in ProcessGDBRemote::Clear (#134397) Currently, these breakpoints are being accumulated every time a new process if created (e.g. through a `run`). Depending on the circumstances, the old breakpoints are even left enabled, interfering with subsequent processes. This is addressed by removing the breakpoints in ProcessGDBRemote::Clear Note that these breakpoints are more of a PlatformDarwin thing, so in the future we should look into moving them there.
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.