Google Git
Sign in
llvm / llvm-project / 31e757d3a124cdcd199a4b1023e136d0b3457b6a
commit31e757d3a124cdcd199a4b1023e136d0b3457b6a[log] [tgz]
authorDavid Spickett <david.spickett@linaro.org>Wed Dec 17 09:01:39 2025 +0000
committerGitHub <noreply@github.com>Wed Dec 17 09:01:39 2025 +0000
tree53d43ba32bf7b701d298d99571c3a5fa67dc6ea0
parent5bfd57e7c9f83d56647a094e605cc15dce6b8d4c [diff]
[lldb][docs] Add register info problems to troubleshooting doc (#171806)

This new section talks about the ways we try to get register
information, how to find out what LLDB decides to do and how to remedy
that choice if needed.

All the methods have their place, so I've tried to present this in the
order we try them. Roughly speaking, each is less accurate than the
previous one. Most people will want to ensure that they're using the XML
from the debug server.

Target definition scripts are the least documented but also most
advanced topic. I have included them because they are the first thing
LLDB checks, but only briefly, as 99.9% of users won't be using one and
should not bother to write one.
1 file changed
tree: 53d43ba32bf7b701d298d99571c3a5fa67dc6ea0
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libsycl/
  16. libunwind/
  17. lld/
  18. lldb/
  19. llvm/
  20. llvm-libgcc/
  21. mlir/
  22. offload/
  23. openmp/
  24. orc-rt/
  25. polly/
  26. runtimes/
  27. third-party/
  28. utils/
  29. .clang-format
  30. .clang-format-ignore
  31. .clang-tidy
  32. .git-blame-ignore-revs
  33. .gitattributes
  34. .gitignore
  35. .mailmap
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. LICENSE.TXT
  39. pyproject.toml
  40. README.md
  41. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

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.

Getting the Source Code and Building LLVM

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.

Getting in touch

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.