[lldb] Adapt lldb tests to changes in 71cdb8c6f144
TestIgnoredExceptions.py needs support from debugserver, so itneeds to be marked skip if out of tree debugserver.
[lldb] Use assertState in TestIgnoredExceptions
[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] Use assertState in more tests (NFC)Follow to D127355, converting more `assertEquals` to `assertState`.Differential Revision: https://reviews.llvm.org/D127378
Convert the test file for TestIgnoredExceptions.py to the mach_vm API.The previous version of this test uses mprotect, and that seemed to beflakey on older systems. I converted the test to use th
Convert the test file for TestIgnoredExceptions.py to the mach_vm API.The previous version of this test uses mprotect, and that seemed to beflakey on older systems. I converted the test to use the underlyingmach_vm API's. The test only runs on Darwin anyway, so this is not areal limitation, and I'm hoping the lower level API's work moreconsistently.
Add some diagnostics to diagnose bot-only failures for TestIgnoredExceptions.pyThe test for commit bff4673b41781ec5bff6b96b52cf321d2271726c is failing on theGreenDragon bot but none of us can repr
Add some diagnostics to diagnose bot-only failures for TestIgnoredExceptions.pyThe test for commit bff4673b41781ec5bff6b96b52cf321d2271726c is failing on theGreenDragon bot but none of us can repro the failure locally. Adding some loggingto the test failure to help diagnose the issue.
Add a darwin platform setting to specify which exceptions debugservershould not receive as exceptions (some will get converted to BSDsignals instead). This is really the only stable way to ensure
Add a darwin platform setting to specify which exceptions debugservershould not receive as exceptions (some will get converted to BSDsignals instead). This is really the only stable way to ensure thata Mach exception gets converted to it's equivalent BSD signal. Forprograms that rely on BSD signal handlers, this has to happen or youcan't even get the program to invoke the signal handler when underthe debugger.This builds on a previous solution to this problem which required youstart debugserver with the -U flag. This was not very discoverableand required lldb be the one to launch debugserver, which is not alwaysthe case.Differential Revision: https://reviews.llvm.org/D125434