Windows: support `DoLoadImage`This implements `DoLoadImage` and `UnloadImage` in the Windows platformplugin modelled after the POSIX platform plugin. This was previouslyunimplemented and resulte
Windows: support `DoLoadImage`This implements `DoLoadImage` and `UnloadImage` in the Windows platformplugin modelled after the POSIX platform plugin. This was previouslyunimplemented and resulted in a difficult to decipher error without anylogging.This implementation is intended to support enables the use of LLDB'sSwift REPL on Windows.Paths which are added to the library search path are persistent andapplied to all subsequent loads. This can be adjusted in the future bystoring all the cookies and restoring the path prior to returning fromthe helper. However, the dynamic path count makes this a bit morechallenging.Reviewed By: @JDevlieghereDifferential Revision: https://reviews.llvm.org/D77287
show more ...
test: add a lit configuration for Windows subdirectoryThis adds a local configuration to the Windows subdirectory to filterout the tests on non-Windows platforms using the lit filtering.
[test] Replace `yaml2obj >` with `yaml2obj -o` and remove unneeded input redirection
Remove 'process launch failed:' message prefix in Target::LaunchSB API clients can describe the failure message in a more naturalway for their UI, this doesn't add information for them.Different
Remove 'process launch failed:' message prefix in Target::LaunchSB API clients can describe the failure message in a more naturalway for their UI, this doesn't add information for them.Differential Revision: https://reviews.llvm.org/D74585<rdar://problem/49953304>
[LLDB] [Windows] Fix Windows-specific race condition in LLDB for session lifetimeThis can e.g. happen if the debugged executable exits before the initialstop, e.g. if it fails to load dependent DL
[LLDB] [Windows] Fix Windows-specific race condition in LLDB for session lifetimeThis can e.g. happen if the debugged executable exits before the initialstop, e.g. if it fails to load dependent DLLs.Add a virtual destructor to ProcessDebugger and let it clean up thesession, and make ProcessWindows::OnExitProcess callProcessDebugger::OnExitProcess for shared parts.Fix suggestion by Adrian McCarthy.Differential Revision: https://reviews.llvm.org/D69503
Re-land "[test] Split LLDB tests into API, Shell & Unit"The original patch got reverted because it broke `check-lldb` on a cleanbuild. This fixes that.llvm-svn: 374201
Revert [test] Split LLDB tests into API, Shell & Unitas it appears to have broken check-lldb.This reverts r374184 (git commit 22314179f0660c172514b397060fd8f34b586e82)llvm-svn: 374187
[test] Split LLDB tests into API, Shell & UnitLLDB has three major testing strategies: unit tests, tests that exercisethe SB API though dotest.py and what we currently call lit tests. Thelater is
[test] Split LLDB tests into API, Shell & UnitLLDB has three major testing strategies: unit tests, tests that exercisethe SB API though dotest.py and what we currently call lit tests. Thelater is rather confusing as we're now using lit as the driver for allthree types of tests. As most of this grew organically, the directorystructure in the LLDB repository doesn't really make this clear.The 'lit' tests are part of the root and among these tests there's aUnit and Suite folder for the unit and dotest-tests. This layout makesit impossible to run just the lit tests.This patch changes the directory layout to match the 3 testingstrategies, each with their own directory and their own configurationfile. This means there are now 3 directories under lit with 3corresponding targets: - API (check-lldb-api): Test exercising the SB API. - Shell (check-lldb-shell): Test exercising command line utilities. - Unit (check-lldb-unit): Unit tests.Finally, there's still the `check-lldb` target that runs all three testsuites.Finally, this also renames the lit folder to `test` to match the LLVMrepository layout.Differential revision: https://reviews.llvm.org/D68606llvm-svn: 374184