llvm-project.git/lldb/test/API/python_api/thread, branch users/mingmingl-llvm/spr/sdpglobalvariable Unnamed repository; edit this file 'description' to name the repository. [lldb][test] Fix instruction test step on Windows 2024-07-10T11:22:07+00:00 David Spickett david.spickett@linaro.org 2024-07-10T11:19:55+00:00 3e06392c7db0eacfca94a176d430d9988b3ffbd6 On Windows the function name is the full prototype including the calling convention, all we care about is that the last part is correct. This also reverts the xfail added by 07b3e2c0c68b93a3d4d89426dc7fd14cc31ca6be. 
On Windows the function name is the full prototype including
the calling convention, all we care about is that the last part
is correct.

This also reverts the xfail added by 07b3e2c0c68b93a3d4d89426dc7fd14cc31ca6be.
[LLDB] XFail on Windows TestThreadAPI.py test_StepInstruction 2024-07-04T10:59:05+00:00 Muhammad Omair Javaid omair.javaid@linaro.org 2024-07-04T10:55:43+00:00 07b3e2c0c68b93a3d4d89426dc7fd14cc31ca6be TestThreadAPI.py test_StepInstruction started failing after #97493 Following assertion fails but I am not sure if test will pass after changing the test. AssertionError: 'void __cdecl call_me(bool)' != 'call_me(bool)' I have marked it as xfail I ll run it on a Windows machine to find an appropriate fix. https://lab.llvm.org/buildbot/#/builders/141/builds/476 
TestThreadAPI.py test_StepInstruction started failing after #97493

Following assertion fails but I am not sure if test will pass after
changing the test.

AssertionError: 'void __cdecl call_me(bool)' != 'call_me(bool)'

I have marked it as xfail I ll run it on a Windows machine to find
an appropriate fix.

https://lab.llvm.org/buildbot/#/builders/141/builds/476
SBThread::StepInstruction shouldn't discard other plans (#97493) 2024-07-03T17:45:20+00:00 jimingham jingham@apple.com 2024-07-03T17:45:20+00:00 845dee36ba4161df153ba05009cea615e20eda5a This was just a typo, none of the external execution control functions should discard other plans. In particular, it means if you stop in a hand-called function and step an instruction, the function call thread plan gets unshipped, popping all the function call frames. I also added a test that asserts the correct behavior. I tested all the stepping operations even though only StepInstruction was wrong. 
This was just a typo, none of the external execution control functions
should discard other plans. In particular, it means if you stop in a
hand-called function and step an instruction, the function call thread
plan gets unshipped, popping all the function call frames.

I also added a test that asserts the correct behavior. I tested all the
stepping operations even though only StepInstruction was wrong.
 [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] Accept negative indexes in __getitem__ 2023-02-08T18:46:26+00:00 Dave Lee davelee.com@gmail.com 2023-02-03T16:45:44+00:00 3ff636729d067801039b3a37618f6ce0dd1c3d24 To the Python bindings, add support for Python-like negative indexes. While was using `script`, I tried to access a thread's bottom frame with `thread.frame[-1]`, but that failed. This change updates the `__getitem__` implementations to support negative indexes as one would expect in Python. Differential Revision: https://reviews.llvm.org/D143282 
To the Python bindings, add support for Python-like negative indexes.

While was using `script`, I tried to access a thread's bottom frame with
`thread.frame[-1]`, but that failed. This change updates the `__getitem__`
implementations to support negative indexes as one would expect in Python.

Differential Revision: https://reviews.llvm.org/D143282
[LLDB] Remove __future__ imports from tests 2022-08-15T08:54:06+00:00 David Spickett david.spickett@linaro.org 2022-08-12T10:56:09+00:00 193259cbcec77add8e189c4dedeefb15fef50d5e Not needed now that we require python 3. Reviewed By: kastiglione, JDevlieghere Differential Revision: https://reviews.llvm.org/D131761 
Not needed now that we require python 3.

Reviewed By: kastiglione, JDevlieghere

Differential Revision: https://reviews.llvm.org/D131761
[lldb] Add assertStopReason helper function 2022-08-03T18:44:13+00:00 Jonas Devlieghere jonas@devlieghere.com 2022-08-03T18:42:12+00:00 0f821339dad1bf45dd71a1cac32b6352ba251ecb Add a function to make it easier to debug a test failure caused by an unexpected stop reason. This is similar to the assertState helper that was added in ce825e46743b. Before: self.assertEqual(stop_reason, lldb.eStopReasonInstrumentation) AssertionError: 5 != 10 After: self.assertStopReason(stop_reason, lldb.eStopReasonInstrumentation) AssertionError: signal (5) != instrumentation (10) Differential revision: https://reviews.llvm.org/D131083 
Add a function to make it easier to debug a test failure caused by an
unexpected stop reason. This is similar to the assertState helper that
was added in ce825e46743b.

Before:

  self.assertEqual(stop_reason, lldb.eStopReasonInstrumentation)
  AssertionError: 5 != 10

After:

  self.assertStopReason(stop_reason, lldb.eStopReasonInstrumentation)
  AssertionError: signal (5) != instrumentation (10)

Differential revision: https://reviews.llvm.org/D131083
[LLDB] Fix TestThreadAPI.py for AArch64/Windows 2022-07-13T11:30:09+00:00 Muhammad Omair Javaid omair.javaid@linaro.org 2022-07-13T11:28:25+00:00 7610524af3c99e63ec6b3a452c45af51ffae57fa This patch fixes TestThreadAPI for AArch64 windows by switching over to PDB debug info instead of DWARF. This is needed to step over library functions like printf as there is debug info mismatch between DWARF and PDB. PDB DWARF interworking is not fully supported by LLDB at the moment. 
This patch fixes TestThreadAPI for AArch64 windows by switching over to
PDB debug info instead of DWARF. This is needed to step over library
functions like printf as there is debug info mismatch between DWARF and
PDB. PDB DWARF interworking is not fully supported by LLDB at the
moment.
[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
[lldb] Use assertState in more tests (NFC) 2022-06-09T23:18:07+00:00 Dave Lee davelee.com@gmail.com 2022-06-09T05:22:27+00:00 47c4c6a7469f3fd3e364a9b3669838686d4f1de6 Follow to D127355, converting more `assertEquals` to `assertState`. Differential Revision: https://reviews.llvm.org/D127378 
Follow to D127355, converting more `assertEquals` to `assertState`.

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