Re: [cdt-debug-dev] Multithread debugging

[Fabian Cenedese <Cenedese@xxxxxxxx>]

>> GDB assumes that if one thread is stopped the whole application is
>> stopped (e.g. on a breakpoint). In an embedded system this isn't always
>> the case. We have a true multitasking system and every task can be
>> stopped, debugged and run again, also several simultaneously. Eclipse
>> also has the gdb philosophy, if one thread is stopped then all are.
>> 
>> Assuming I can either change gdb or use another debugger which supports
>> the fully multitasking philosophy, how much work would be needed to
>> change eclipse/CDT to work with this?
>
>It should work now.  When we become suspended
>we send a suspended event with the source of the event being the Target.
>It tells Eclipse/CDT that the target is suspended i.e. all the threads
>are suspended.  If we have a suspended event with a thread as the source
>then only this thread is suspended.

I guess I will have to do some more testing then. Thanks.

>We are looking at writing documentation for this, but also the debug interfaces
>are going through an overall:
>
>- The interface to the CDT Launcher
>- The interface to CDI; interface that Eclipse/CDT is using to exchange
>  with the backend (for example GDB).
>- Change to the MI, to adapt to MI level 2
>- some 0yving patches 8-)
>- etc ...
>
>So your timing is ... not good, unless you have a few free cycles and
>want to participate.

I've seen your other announcement, so I'm pleased that it is going in our
direction :) I would love to help but I'm a newbie to eclipse and all its
internas as well as Java (coming from the c/c++ world). But I will continue
to look into it and if I find something I'll let you know :)

Thanks

bye  Fabi