[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] Replace asserts on .Success() with assertSuccess()Replace forms of `assertTrue(err.Success())` with `assertSuccess(err)` (added in D82759).* `assertSuccess` prints out the error's message
[lldb] Replace asserts on .Success() with assertSuccess()Replace forms of `assertTrue(err.Success())` with `assertSuccess(err)` (added in D82759).* `assertSuccess` prints out the error's message* `assertSuccess` expresses explicit higher level semantics, both to the reader and for test failure output* `assertSuccess` seems not to be well known, using it where possible will help spread knowledge* `assertSuccess` statements are more succinctDifferential Revision: https://reviews.llvm.org/D119616
[lldb] NFC: Fix trivial typo in comments, documents, and messagesDifferential Revision: https://reviews.llvm.org/D77460
[lldb/testsuite] Skip part of TestProcessCrashInfo.py on Darwin embeddedSee https://reviews.llvm.org/D76407 for discussion.
[lldb/test] Skip running a test under ASan, it intentionally double-frees
[lldb/Plugins] Move SBTarget::GetExtendedCrashInformation to SBProcessThis patch moves the SB API method GetExtendedCrashInformation fromSBTarget to SBProcess since it only makes sense to call thi
[lldb/Plugins] Move SBTarget::GetExtendedCrashInformation to SBProcessThis patch moves the SB API method GetExtendedCrashInformation fromSBTarget to SBProcess since it only makes sense to call this method on asane process which might not be the case on a SBTarget object.It also addresses some feedbacks received after landing the first patchfor the 'crash-info' feature.Differential Revision: https://reviews.llvm.org/D75049Signed-off-by: Med Ismail Bennani <[email protected]>
[lldb/Plugins] Add ability to fetch crash information on crashed processesCurrently, in macOS, when a process crashes, lldb halts inside theimplementation disassembly without yielding any useful i
[lldb/Plugins] Add ability to fetch crash information on crashed processesCurrently, in macOS, when a process crashes, lldb halts inside theimplementation disassembly without yielding any useful information.The only way to get more information is to detach from the process, then waitfor ReportCrash to generate a report, find the report, then see what errormessage was included in it. Instead of waiting for this to happen, lldb couldlocate the error_string and make it available to the user.This patch addresses this issue by enabling the user to fetch extendedcrash information for crashed processes using `process status --verbose`.Depending on the platform, this will try to gather different crash informationinto an structured data dictionnary. This dictionnary is generic and extensible,as it contains an array for each different type of crash information.On Darwin Platforms, lldb will iterate over each of the target's images,extract their `__crash_info` section and generated a StructuredData::Arraycontaining, in each entry, the module spec, its UUID, the crash messagesand the abort cause. The array will be inserted into the platform's`m_extended_crash_info` dictionnary and `FetchExtendedCrashInformation` willreturn its JSON representation like this:```{ "crash-info annotations": [ { "abort-cause": 0, "image": "/usr/lib/system/libsystem_malloc.dylib", "message": "main(76483,0x1000cedc0) malloc: *** error for object 0x1003040a0: pointer being freed was not allocated", "message2": "", "uuid": "5747D0C9-900D-3306-8D70-1E2EA4B7E821" }, ... ], ...}```This crash information can also be fetched using the SB API or lldb-rpc protocolusing SBTarget::GetExtendedCrashInformation().rdar://37736535Differential Revision: https://reviews.llvm.org/D74657Signed-off-by: Med Ismail Bennani <[email protected]>