[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] Convert more assertTrue to assertEqual (NFC)Follow up to D95813, this converts multiline assertTrue to assertEqual.Differential Revision: https://reviews.llvm.org/D95899
[lldb/testsuite] un-XFail TestInlineStepping.py on linux and windowsIt looks like my tweak in ecc6c426977f5 made the test pass on windowsand the linux aarch64 bot.
[lldb/testsuite] Fix TestInlineStepping on arm64 with newer compilersSummary:TestInlineStepping tests LLDB's ability to step in the presence ofinline frames. The testcase source has a number of f
[lldb/testsuite] Fix TestInlineStepping on arm64 with newer compilersSummary:TestInlineStepping tests LLDB's ability to step in the presence ofinline frames. The testcase source has a number of functions and someof them are marked `always_inline`.The test is built around the assumption that the inline function willbe fully represented once inlined, but this is not true with thecurrent arm64 code generation. For example:void caller() { always_inline_function(); // Step here}When stppeing into `caller()` above, you might immediatly end up inthe inlines frame for `always_inline_function()`, because there mightliterally be no code associated with `caller()` itself.This patch hacks around the issue by adding an `asm volatile("nop")`on some lines with inlined calls where we expect to be able tostep. Like so:void caller() { asm volatile("nop"); always_inline_function(); // Step here}This guarantees there is always going to be one instruction for thisline in the caller.Reviewers: labath, jinghamSubscribers: kristof.beyls, danielkiss, lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D76406
[lldb][test] Remove symlink for API tests.Summary: Moves lldbsuite tests to lldb/test/API.This is a largely mechanical change, moved with the following steps:```rm lldb/test/API/testcasesmkdi
[lldb][test] Remove symlink for API tests.Summary: Moves lldbsuite tests to lldb/test/API.This is a largely mechanical change, moved with the following steps:```rm lldb/test/API/testcasesmkdir -p lldb/test/API/{test_runner/test,tools/lldb-{server,vscode}}mv lldb/packages/Python/lldbsuite/test/test_runner/test lldb/test/API/test_runnerfor d in $(find lldb/packages/Python/lldbsuite/test/* -maxdepth 0 -type d | egrep -v "make|plugins|test_runner|tools"); do mv $d lldb/test/API; donefor d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-vscode -maxdepth 1 -mindepth 1 | grep -v ".py"); do mv $d lldb/test/API/tools/lldb-vscode; donefor d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-server -maxdepth 1 -mindepth 1 | egrep -v "gdbremote_testcase.py|lldbgdbserverutils.py|socket_packet_pump.py"); do mv $d lldb/test/API/tools/lldb-server; done```lldb/packages/Python/lldbsuite/__init__.py and lldb/test/API/lit.cfg.py were also updated with the new directory structure.Reviewers: labath, JDevlieghereTags: #lldbDifferential Revision: https://reviews.llvm.org/D71151