diff options
| author | Jason Molenda <jason@molenda.com> | 2023-01-18 12:29:52 -0800 |
|---|---|---|
| committer | Jason Molenda <jason@molenda.com> | 2023-01-18 12:33:05 -0800 |
| commit | db223b7f01f70cbd8459d0db9b20dfe9a3b099a7 (patch) | |
| tree | 66b20795340acf379b6c5ea5392adeafddce858e /clang/lib/Frontend/TestModuleFileExtension.cpp | |
| parent | 5d98dc7124dcf1cc231b7fc67fb55b528a3e493d (diff) | |
| download | llvm-db223b7f01f70cbd8459d0db9b20dfe9a3b099a7.zip llvm-db223b7f01f70cbd8459d0db9b20dfe9a3b099a7.tar.gz llvm-db223b7f01f70cbd8459d0db9b20dfe9a3b099a7.tar.bz2 | |
Do qProcessInfo-hint binary loading later in Process setup
The remote stub may give lldb hints about binaries to
be loaded, especially in a firmware type environment, and
relay those hints in the qProcessInfo response. The
binary loading was done very early in Process setup, before
we had any threads, and this made it complicated for people
to write dSYM python scripts which need access to a thread.
Delay the binary loading until a bit later in the Process
startup.
Differential Revision: https://reviews.llvm.org/D141972
rdar://104235301
Diffstat (limited to 'clang/lib/Frontend/TestModuleFileExtension.cpp')
0 files changed, 0 insertions, 0 deletions