RE: [cdt-debug-dev] determining which breakpoint was hit

["Gustafson, Geoffrey R" <geoffrey.r.gustafson@xxxxxxxxx>]

>> I will start looking at internals and GDB MI interface to see if I
can 
>> find a temporary solution.
>
> The fix is to emulate this by getting all the threads and fire a
suspend event
> for all of them.

The part I'm really looking for is finding which IBreakpoint was hit,
causing
the suspend event.

Looking into it more, I see that CThread's getBreakpoints() just returns
null,
so I'm pretty sure the information is just not available publicly in CDT
1.2.

Happily, in the MIBreakpointHitEvent class, the bkptno member is already
there
that contains the GDB breakpoint ID. I'm assuming CDT uses these IDs to
talk
with GDB, and so there will probably be some way to map that number back
to
the corresponding IBreakpoint.

I'll keep looking at it and hope to provide a patch for a future CDT.

Thanks,

Geoff

[My opinions do not necessarily reflect those of my employer.]