llvm-project.git/lldb/test/API/commands/target/basic/TestTargetCommand.py, branch main

[lldb] fix(lldb/**.py): fix invalid escape sequences (#94034)

2025-02-28T14:59:35+00:00

Co-authored-by: Eisuke Kawashima

[lldb] Fixed TestTargetCommand.py in case of Windows host and Linux target (#115470)

2024-11-08T14:11:59+00:00

Fixed TestTargetCommand.py in case of Windows host and Linux target.

Clarify error messages on corefiles that no plugin handles (#72559)

2023-11-16T21:58:07+00:00

These error messages are written in a way that makes sense to an lldb
developer, but not to an end user who asks lldb to run on a compressed
corefile or whatever. Simplfy the messages.

[NFC][Py Reformat] Reformat python files in lldb

2023-05-25T19:54:09+00:00

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 ` 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

[lldb] Skip target variable tests on Darwin because of chained fixups

2022-08-12T17:23:15+00:00

When targeting macOS Ventura, ld64 will use authenticated fixups for
x86_64 as well as arm64 (where that has always been the case). This
results in test failures when using an Xcode 14 toolchain on an Intel
mac running macOS Ventura:

  Failed Tests (3):
    lldb-api :: commands/target/basic/TestTargetCommand.py
    lldb-api :: lang/c/global_variables/TestGlobalVariables.py
    lldb-api :: lang/cpp/char8_t/TestCxxChar8_t.py

Rather than trying to come up with a sophisticated decorator based off
the deployment target, I marked them all as skipped with a comment
explaining why.

Differential revision: https://reviews.llvm.org/D131741

Have CommandObjectParsed check for "commands that take no arguments".

2022-06-27T22:14:41+00:00

This is currently being done in an ad hoc way, and so for some
commands it isn't being checked.  We have the info to make this check,
since commands are supposed to add their arguments to the m_arguments
field of the CommandObject.  This change uses that info to check whether
the command received arguments in error.

A handful of commands weren't defining their argument types, I also had
to fix them.  And a bunch of commands were checking for arguments by
hand, so I removed those checks in favor of the CommandObject one.  That
also meant I had to change some tests that were checking for the ad hoc
error outputs.

Differential Revision: https://reviews.llvm.org/D128453

[lldb][tests] Automatically call compute_mydir (NFC)

2022-06-17T21:34:49+00:00

Eliminate boilerplate of having each test manually assign to `mydir` by calling
`compute_mydir` in lldbtest.py.

Differential Revision: https://reviews.llvm.org/D128077

[lldb] [test] Update baseline test status for FreeBSD

2022-06-17T12:35:18+00:00

Fixes #19721
Fixes #18440
Partially fixes bug #47660
Fixes #47761
Fixes #47763

Sponsored by: The FreeBSD Foundation

[lldb] Correctly display the number of types found

2022-01-15T18:31:49+00:00

Correctly display the number of types found for `target modules lookup
--type` and add a test.

Fixes #53219

[lldb] Skip tests for target var without a proc on both arm64 & arm64e

2021-10-26T03:45:38+00:00

LLDB needs to be taught about chained fixups.