llvm-project.git/lldb/test/API/iohandler, branch main Unnamed repository; edit this file 'description' to name the repository. [lldb][NFC] update API tests which skip/expect-fail arm 2025-05-28T01:41:16+00:00 Jason Molenda jmolenda@apple.com 2025-05-28T01:37:26+00:00 6d6feaf7e3ce559f69477b8d682cffb63336ca53 The architectures provided to skipIf / expectedFail are regular expressions (v. _match_decorator_property() in decorators.py so on Darwin systems "arm64" would match the skips for "arm" (32-bit Linux). Update these to "arm$" to prevent this, and also update three tests (TestBuiltinFormats.py, TestCrossDSOTailCalls.py, TestCrossObjectTailCalls.py) that were skipped for arm64 via this behavior, and need to be skipped or they will fail. This was moviated by the new TestDynamicValue.py test which has an expected-fail for arm, but the test was passing on arm64 Darwin resulting in failure for the CIs. 
The architectures provided to skipIf / expectedFail are regular
expressions (v. _match_decorator_property() in decorators.py
so on Darwin systems "arm64" would match the skips for "arm" (32-bit
Linux).  Update these to "arm$" to prevent this, and also update
three tests (TestBuiltinFormats.py, TestCrossDSOTailCalls.py,
TestCrossObjectTailCalls.py) that were skipped for arm64 via this
behavior, and need to be skipped or they will fail.

This was moviated by the new TestDynamicValue.py test which has
an expected-fail for arm, but the test was passing on arm64 Darwin
resulting in failure for the CIs.
[lldb] Move lldb_enable_attach from test_common to a separate header (#139550) 2025-05-13T15:52:23+00:00 Pavel Labath pavel@labath.sk 2025-05-13T15:52:23+00:00 91ea49499325aeff8426135721b1bd432e5b7780 test_common is force-included into every compilation, which causes problems when we're compiling assembly code, as we were in #138805. This avoids that as we can include the header only when it's needed. 
test_common is force-included into every compilation, which causes
problems when we're compiling assembly code, as we were in #138805.

This avoids that as we can include the header only when it's needed.
 [lldb] Require wide char support in unicode test (#131951) 2025-03-19T15:17:59+00:00 David Peixotto peix@meta.com 2025-03-19T15:17:59+00:00 58027fa989391451d7eaa21fe24c135bcad52e79 The unicode test sends some unicode input to lldb through pexpect and expects the output to be echoed back in an error message. This only works correctly when editline was compiled with wide character support. This commit modifies the test to require the necessary libedit configuration. 
The unicode test sends some unicode input to lldb through pexpect and
expects the output to be echoed back in an error message. This only
works correctly when editline was compiled with wide character support.

This commit modifies the test to require the necessary libedit
configuration.
 [lldb] fix(lldb/**.py): fix invalid escape sequences (#94034) 2025-02-28T14:59:35+00:00 Eisuke Kawashima e.kawaschima+github@gmail.com 2025-02-28T14:59:35+00:00 24abf2c7285df7b5c1b442df10cd0b090a841358 Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com> 
Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com>
 [lldb] Disable TestIOHandlerResizeNoEditline.py for Windows hosts (#120025) 2024-12-16T15:52:30+00:00 Dmitry Vasilyev dvassiliev@accesssoftek.com 2024-12-16T15:52:30+00:00 d576021853fd64c10fd746389a9b263cf10c5295 See #120021 for details. 
See #120021 for details.
 [lldb][Windows] Fixed the TestIOHandlerResizeNoEditline test (#92286) 2024-05-15T17:08:35+00:00 Dmitry Vasilyev dvassiliev@accesssoftek.com 2024-05-15T17:08:35+00:00 d92c67784f21063d6334a009dbf4f9e0f8217b41 This test caused python crash on Windows x86_64 host with the exit code 0xC0000409 (STATUS_STACK_BUFFER_OVERRUN). Close the input stream before exit to avoid this crash. 
This test caused python crash on Windows x86_64 host with the exit code
0xC0000409 (STATUS_STACK_BUFFER_OVERRUN). Close the input stream before
exit to avoid this crash.
 Skip various tests under ASAN on green dragon (#90531) 2024-04-29T22:56:41+00:00 Adrian Prantl aprantl@apple.com 2024-04-29T22:56:41+00:00 1b70580dd867195b0442e582eccd42abc41ee12d using the macOS version as a proxy. I can't reproduce any of these failures locally, but the tests all use pexpect and probably have bad timeout behavior under high load. 
using the macOS version as a proxy. I can't reproduce any of these
failures locally, but the tests all use pexpect and probably have bad
timeout behavior under high load.
 Fix a bug in handling ^C at the "y/n/a" completion prompt. 2023-09-28T00:20:48+00:00 Jim Ingham jingham@apple.com 2023-09-28T00:07:33+00:00 0f339e6567bffb290e409ef5de272fb75ce70234 We just forget to check for interrupt while waiting for the answer to the prompt. But if we are in the interrupt state then the lower layers of the EditLine code just eat all characters so we never get out of the query prompt. You're pretty much stuck and have to kill lldb. The solution is to check for the interrupt. The patch is a little bigger because where I needed to check the Interrupt state I only had the ::EditLine object, but the editor state is held in lldb's EditLine wrapper, so I had to do a little work to get my hands on it. 
We just forget to check for interrupt while waiting for the answer to the prompt. But if we are in the interrupt state then the lower
layers of the EditLine code just eat all characters so we never get out of the query prompt. You're pretty much stuck and have to kill lldb.

The solution is to check for the interrupt. The patch is a little bigger because where I needed to check the Interrupt state I only
had the ::EditLine object, but the editor state is held in lldb's EditLine wrapper, so I had to do a little work to get my hands on it.
[NFC][Py Reformat] Reformat python files in lldb 2023-05-25T19:54:09+00:00 Jonas Devlieghere jonas@devlieghere.com 2023-05-25T15:48:57+00:00 2238dcc39358353cac21df75c3c3286ab20b8f53 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 
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
[lldb][tests] Automatically call compute_mydir (NFC) 2022-06-17T21:34:49+00:00 Dave Lee davelee.com@gmail.com 2022-06-17T00:38:47+00:00 4cc8f2a017c76af25234afc7c380550e9c93135c Eliminate boilerplate of having each test manually assign to `mydir` by calling `compute_mydir` in lldbtest.py. Differential Revision: https://reviews.llvm.org/D128077 
Eliminate boilerplate of having each test manually assign to `mydir` by calling
`compute_mydir` in lldbtest.py.

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