Hi Enrico and Jim,
My lldb is 179.5 on mountain lion
What I did for the good result
File “xxx”
B main
R
Program stops at breakpoint and print thread and frame information.
For bad result
File “xxx”
B main
Command script import a.py
R
Process 10786 launched: ‘xxx’ (x86_64)
In the a.py
Def __lldb_init_module (debugger, dict):
Debugger.SetAsync(False)
This is about what I did.
Thanks,
Yin
From: Enrico Granata [mailto:[email protected]]
Sent: Wednesday, September 25, 2013 5:48 PM
To: Yin Ma
Cc: lldb-dev
Subject: Re: [lldb-dev] Question on SetAsync(False) Mode
First of all the obvious
Have you checked that your breakpoint is getting hit at all?
For instance, did you manually run lldb, set the breakpoint, and then run, and
watch LLDB actually stop there?
If not, it seems a worthy initial test
If that works, more repro steps might be necessary to figure this out.
What inferior are you using? What does your script do exactly? That kind of
information
Enrico Granata
📩 egranata@.com
☎️ 27683
On Sep 25, 2013, at 5:34 PM, Yin Ma <[email protected]> wrote:
Hello,
What I want is to run a command and return to lldb only after
This command finishes. This should be the behavior of
synchronous mode. So I called
debugger.SetAsync(False)
right after lldb starts. However, I never get what
I expected. I set breakpoint and run. The process
Never stops, it just shows process exited.
Based on the webpage, it says:
When we step or continue, don't return from the function
Until the process stops.
So, when process stops at breakpoints, it should return
To lldb. Now it doesn't.
Is this the right behavior? How I can get the behavior
I want?
Thanks,
Yin
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
