[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] determining which breakpoint was hit
|
>
> Is there any way to programmatically determine which breakpoint was hit
> in a CDT 1.2 project?
>
> JDT reports SUSPEND/BREAKPOINT events on the IThread, and specifies the
> relevant breakpoint through the IThread getBreakpoints() method. CDT
> reports the events on the IDebugTarget, and its child IThread objects do
> not provide anything through getBreakpoints().
>
>
The Debugging model provided by GDB, when an application is stopped/suspended all threads
are suspended. So the event source is simply the target, instead of the thread.
And also when debugging non-threaded apps.
This is/(will be) corrected in the next version of CDI(C Debug Interface),
schedule for CDT-2.0, I'm currently writing the doc and will be submitting
drafts later ...
> 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.
