That works, thanks Jim! Agreed that it is ugly though :-)
-Chris
> On Dec 4, 2017, at 6:18 PM, Jim Ingham wrote:
>
> Yup, apparently debugserver tells us the stop is for exec directly so we
> don't treat it as a breakpoint hit. That sorta makes sense, you don't want
> to trigger a breakpoin
Yup, apparently debugserver tells us the stop is for exec directly so we don't
treat it as a breakpoint hit. That sorta makes sense, you don't want to
trigger a breakpoint hit every time you find a thread at the pc of a breakpoint
(might be a thread that hit a breakpoint, then didn't get to run
> On Dec 4, 2017, at 4:25 PM, Chris Lattner wrote:
>> For macOS, you can also just do:
>>
>> (lldb) break set -n _dyld_start --skip-prologue 0 -s dyld
>> Breakpoint 2: where = dyld`_dyld_start, address = 0x0001b19c
>> (lldb) b com add -o continue
>> either in your .lldbinit or in your deb
> On Dec 4, 2017, at 3:50 PM, Jim Ingham wrote:
> There isn't a setting to auto-continue from exec. Definitely should be.
Yeah, I assumed that I could redefine my “r” alias to include this, but there
is no flag to process launch.
>
> If somebody wants to try their hand at it, just add a se
There isn't a setting to auto-continue from exec. Definitely should be.
If somebody wants to try their hand at it, just add a setting in parallel to
stop-on-sharedlibrary-events and then add a ShouldStop to the StopInfoExec
(StopInfo.cpp) that checks this setting. The StopInfoSignal does som
Hi all,
Is there anything I can put into my lldb init script to prevent LLDB from
stopping on exec? Every time I run a program I get this super irritating
behavior:
Thanks for any help!
-Chris
Process 20310 launched:
'/Users/clattner/Projects/build/Xcode-ReleaseAssert+swift-DebugAssert/swi
