Hi there!
I was wondering what the threading model is for the Python API (when
running inside of LLDB, in implementing a command)?
For example: If I create a Python thread in my command, how do I
access the LLDB API? Is there an equivalent of gdb's post_event
function to run it on the main thread
The API is thread safe, but you can run into interesting issues if you don't
thread things right. You don't want one thread stepping and another thread
resuming. It will work, but you probably will have a tough time figuring out
why certain functions return certain values. Also, you don't want o
OK thanks! (If I try to get, for example, the local variables while
the process is running, will that fail or "succeed" in a weird way?)
Christian
On Mon, Aug 5, 2019 at 11:15 AM Greg Clayton wrote:
>
> The API is thread safe, but you can run into interesting issues if you don't
> thread things
> On Aug 5, 2019, at 9:20 AM, Christian Biesinger wrote:
>
> OK thanks! (If I try to get, for example, the local variables while
> the process is running, will that fail or "succeed" in a weird way?)
You will get an empty list. But if you get the list of variables on thread 1,
then thread 2 c
https://bugs.llvm.org/show_bug.cgi?id=42895
Bug ID: 42895
Summary: Segfault on `p $0`
Product: lldb
Version: 8.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Comp
https://bugs.llvm.org/show_bug.cgi?id=42895
Davide Italiano changed:
What|Removed |Added
Assignee|lldb-dev@lists.llvm.org |teempe...@gmail.com
--
You are receiving thi
https://bugs.llvm.org/show_bug.cgi?id=21746
Jonas Devlieghere changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.llvm.org/show_bug.cgi?id=42895
Davide Italiano changed:
What|Removed |Added
Assignee|teempe...@gmail.com |lldb-dev@lists.llvm.org
--- Comment #3 from D
