[lldb-dev] Process stops when two breakpoint are hit simulatenously, even though neither of them wants to stop

Hi folks, I'm using the C++ API to create a breakpoint with callback. In the callback I do some stuff and then always return false, to have the process continue. This works great, except when a breakpoint hit is coincident with another breakpoint (in my case I ran into this with both the jit

Re: [lldb-dev] Thread resumes with stale signal after executing InferiorCallMmap

Hi, I believe the SIGILL problem you are referring to is the problem described in bug . This was fixed in r244875, but unfortunately, this was after 3.7 branch so this patch did not make it there. I recommend to try the master branch, I think this

[lldb-dev] [Bug 25106] New: lldb crashes when reading a core file

https://llvm.org/bugs/show_bug.cgi?id=25106 Bug ID: 25106 Summary: lldb crashes when reading a core file Product: lldb Version: 3.7 Hardware: PC OS: Linux Status: NEW Severity: normal Priority:

Re: [lldb-dev] How to set source line breakpoint using BreakpointCreateByLocation?

> On Oct 7, 2015, at 8:31 PM, Jeffrey Tan via lldb-dev > wrote: > > Hi, > > I am writing a python script to set source line breakpoint in ObjC on Mac > OSX. But > self.debugger.GetSelectedTarget().BreakpointCreateByLocation("EATAnimatedView.m", > line) always fail.

Re: [lldb-dev] lldb fails to hit breakpoint when line maps to multiple addresses

> On Oct 7, 2015, at 5:07 PM, Jim Ingham wrote: > > Another way to do this - which I thought about originally but rejected as too > much delicate machinery for the desired effect - is to add the notion of > "clusters" of locations to the breakpoint. Instead of eliding all