llvm-project.git/lldb/examples/python/in_call_stack.py, branch users/meinersbur/flang_runtime_split-headers Unnamed repository; edit this file 'description' to name the repository. [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] Allow flexible importing of in_call_stack 2022-11-11T22:28:40+00:00 Dave Lee davelee.com@gmail.com 2022-11-11T20:18:37+00:00 307f395d4ffee839dd0bd88c879539428cc31693 Allow `in_call_stack` to be imported in either of the following ways: ``` command script import path/to/in_call_stack.py command script import lldb.utils.in_call_stack ``` rdar://102249295 Differential Revision: https://reviews.llvm.org/D137860 
Allow `in_call_stack` to be imported in either of the following ways:

```
command script import path/to/in_call_stack.py
command script import lldb.utils.in_call_stack
```

rdar://102249295

Differential Revision: https://reviews.llvm.org/D137860
[Examples] Move structured-data unpacking out of the loop. (NFC) 2019-11-22T23:43:39+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-11-22T23:43:39+00:00 b6ae524cd2d5139748e207d4b60b4a900775d6a7 There's no need to repeat this work in the loop. 
There's no need to repeat this work in the loop.
[Examples] Add in_call_stack breakpoint function. 2019-11-22T23:36:42+00:00 Jonas Devlieghere jonas@devlieghere.com 2019-11-22T23:32:43+00:00 1b099c1df00e3c8a0ba20af199c89a154bdb7a45 The in_call_stack Python script makes it possible to modify the last breakpoint to only stop if a given function is present in the call stack. It will check both the symbol name and the function name (coming from the debug info, in case the binary is stripped). To use this, you have to: 1. Import the script into lldb. (lldb) command script import in_call_stack.py 2. Set a breakpoint and use the in_call_stack alias. (lldb) b foo (lldb) in_call_stack bar Note that this alias operates on the last set breakpoint. You can re-run the in_call_stack command to modify the condition. 
The in_call_stack Python script makes it possible to modify the last
breakpoint to only stop if a given function is present in the call
stack. It will check both the symbol name and the function name (coming
from the debug info, in case the binary is stripped).

To use this, you have to:

1. Import the script into lldb.

(lldb) command script import in_call_stack.py

2. Set a breakpoint and use the in_call_stack alias.

(lldb) b foo
(lldb) in_call_stack bar

Note that this alias operates on the last set breakpoint. You can re-run
the in_call_stack command to modify the condition.