forked from OSchip/llvm-project
![]() Support three new keys in the qProcessInfo response from the remote gdb stub to handle the case of attaching to a core running some type of standalone/firmware code and the stub knows the UUID and load address-or-slide for the binary. There will be no proper DynamicLoader plugin in this scenario, but we can try to locate and load the binary into lldb at the correct offset. Differential Revision: https://reviews.llvm.org/D116211 rdar://75191077 |
||
---|---|---|
.. | ||
_lldb | ||
_static | ||
design | ||
man | ||
resources | ||
status | ||
testsuite | ||
use | ||
.htaccess | ||
CMakeLists.txt | ||
conf.py | ||
doxygen-mainpage.dox | ||
doxygen.cfg.in | ||
index.rst | ||
lldb-for-gdb-users.txt | ||
lldb-gdb-remote.txt | ||
lldb-platform-packets.txt | ||
python_api.rst | ||
python_api_enums.rst |