summaryrefslogtreecommitdiff
path: root/lldb/test/API/functionalities/dlopen_other_executable
AgeCommit message (Collapse)Author
2024-10-16[lldb] Support tests with nested make invocations on Windows 2/2 (#112360)Stefan Gränitz
Following up from https://github.com/llvm/llvm-project/pull/112342, we roll out the fix and quote nested `make` invocations in all API tests.
2023-05-25[NFC][Py Reformat] Reformat python files in lldbJonas Devlieghere
This is an ongoing series of commits that are reformatting our Python code. Reformatting is done with `black` (23.1.0). If you end up having problems merging this commit because you have made changes to a python file, the best way to handle that is to run `git checkout --ours <yourfile>` and then reformat it with black. RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style Differential revision: https://reviews.llvm.org/D151460
2022-07-23[lldb] Adapt lldb tests to changes in 71cdb8c6f144Augusto Noronha
2022-06-17[lldb][tests] Automatically call compute_mydir (NFC)Dave Lee
Eliminate boilerplate of having each test manually assign to `mydir` by calling `compute_mydir` in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077
2022-02-14[lldb] Replace asserts on .Success() with assertSuccess()Dave Lee
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 succinct Differential Revision: https://reviews.llvm.org/D119616
2020-12-20[lldb] [test] Update test status for NetBSDMichał Górny
2020-12-07[lldb] [test] Link FreeBSD test failures to bugsMichał Górny
Differential Revision: https://reviews.llvm.org/D92740
2020-11-03[lldb] [test] Update XFAILs/skips for FreeBSDMichał Górny
Update expected failures and test skips based on common results for the old and new FreeBSD plugins.
2020-07-17[lldb] Only set the executable module for a target onceRaphael Isemann
Summary: When we try to find the executable module for our target we don't check if we already have an executable module set. This causes that when debugging a program that dlopens another executable, LLDB will take that other executable as the new executable of the target (which causes that future launches of the target will launch the dlopen'd executable instead of the original executable). This just adds a check that we only set the executable when we haven't already found one. Fixes rdar://63443099 Reviewers: jasonmolenda, jingham, teemperor Reviewed By: jasonmolenda, teemperor Subscribers: jingham, JDevlieghere Differential Revision: https://reviews.llvm.org/D80724