[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 ...
We don't require users to type out the full context of a function, forsymbol name matches. Instead, we extract the incoming path's basename, look up all the symbols with that base name, and then co
We don't require users to type out the full context of a function, forsymbol name matches. Instead, we extract the incoming path's basename, look up all the symbols with that base name, and then comparethe rest of the context that the user provided to make sure itmatches. However, we do this comparison using just a strstr. So forinstance:break set -n foo::barwill match not only "a::foo::bar" but "notherfoo::bar". The former ispretty clearly the user's intent, but I don't think the latter is, andresults in breakpoints picking up too many matches.This change adds a Language::DemangledNameContainsPath API which cando a language aware match against the path provided. If the languagedoesn't provide this we fall back to the strstr (though that's changedto StringRef::contains in the patch).Differential Revision: https://reviews.llvm.org/D124579
[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/ObjectFileMachO] Correctly account for resolver symbolsSummary:The resolver addresses stored in the dyld trie are relative to the baseof the __TEXT segment. This is usually 0 in a dylib, so
[lldb/ObjectFileMachO] Correctly account for resolver symbolsSummary:The resolver addresses stored in the dyld trie are relative to the baseof the __TEXT segment. This is usually 0 in a dylib, so this was nevernoticed, but it is not 0 for most dylibs integrated in the shared cache.As we started using the shared cache images recently as symbol source,this causes LLDB to fail to resolve symbols which go through a runtimeresolver.Reviewers: jasonmolenda, jinghamSubscribers: lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D84083
[TestIndirectSymbol] This tests an Apple-specific feature.Remove a redundant check.
[TestIndirectSymbols] This now runs and works on iOS (arm64).
[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