[Lldb-commits] [PATCH] LLDB AddressSanitizer break on error and report data extraction

jingham at apple.com jingham at apple.com
Tue Oct 7 12:11:34 PDT 2014


eStopReasonException is a Mach exception.  When you hit a breakpoint the Mach Exception with type EXC_BREAKPOINT is the actual stop reason, but this gets translated to eStopReasonBreakpoint if it the stop address is one of our breakpoints.  Similarly on Linux, you'd get an eStopReasonSignal/SIGTRAP, which would get translated to eStopReasonBreakpoint if the address was at one of our breakpoints.  The eStopReasonInstrumentation is analogous.  You stop for some system specific reason, which you then identify as an instrumentation stop, so you convert the stop reason from a general one to one specific to the event that occurred.

Jim

> On Oct 3, 2014, at 2:02 PM, Kuba Brecka <kuba.brecka at gmail.com> wrote:
> 
> On the other, I'm not sure about the new stop reason enum value (eStopReasonInstrumentation), maybe I should just reuse eStopReasonException. At least for AddressSanitizer, these stops practically *are* exceptions.
> 
> http://reviews.llvm.org/D5592
> 
> 




More information about the lldb-commits mailing list