[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://r
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077
show more ...
[lldb] Fix TestDyldExecLinux with xml enabledNativeProcessLinux is not able to properly read libraries-svr4 data whenrunning with ld.so as the "main" executable. Normally, this is not a bigproble
[lldb] Fix TestDyldExecLinux with xml enabledNativeProcessLinux is not able to properly read libraries-svr4 data whenrunning with ld.so as the "main" executable. Normally, this is not a bigproblem, as it returns an error message, and lldb can fallback to manuallibrary loading.Unfortunately, lldb-server also does not clear cached svr4 data on exec,which means that it does *not* return an error when the applicationexecs from the "regular" to the "ld.so" mode. Instead it returnsincorrect data (it is missing the main executable) and causesTestDyldExecLinux to fail (but only when building with xml supportenabled).This patch makes ensures that cached process data is cleared on exec,fixing the test. Since TestDyldExecLinux has shown to be sensitive tothe way we read library info, I fork it into two (with svr4 enabled anddisabled).
[lldb] Use assertState in more tests (NFC)Follow to D127355, converting more `assertEquals` to `assertState`.Differential Revision: https://reviews.llvm.org/D127378
Add the ability to debug through an exec into ldA previous commit enabled LLDB to be able to debug a program launched via ld: https://reviews.llvm.org/D108061.This commit adds the ability to debu
Add the ability to debug through an exec into ldA previous commit enabled LLDB to be able to debug a program launched via ld: https://reviews.llvm.org/D108061.This commit adds the ability to debug a program launched via ld when it happens during an exec into the dynamic loader. There was an issue where after the exec we would locate the rendezvous structure right away but it didn't contain any valid values and we would try to set the dyanamic loader breakpoint at address zero. This patch fixes that and adds a test.Differential Revision: https://reviews.llvm.org/D125253