[cdt-debug-dev] Multithread debugging

[Fabian Cenedese <Cenedese@xxxxxxxx>]

Hi

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?

What I would need:

- Every thread has a state independently of other threads
- A running thread can change variables which should be observable
  (and not only while the thread is stopped)
- For this reason some kind of global refresh is necessary which would
  refresh stuff as registers, task states, variables in the watches etc
  independently of any thread state
- I can debug every thread independently of others, e.g. three threads
  are stopped on a breakpoint, I can single-step thread 1, then thread 2,
  then again thread 1, then run thread 2, single-step thread 3, single-step
  thread 1, stop thread 2, run thread 1, run thread 3 etc.
- The possibility to attach to an already running (and possibly halted)
  system and read its states, already set breakpoints, variables etc

Thanks

bye  Fabi