[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] Debugging multiple core microcontrollers.
|
>
> b) we could write one version of gdb to handle both processors, but I
> think it would be a nightmare. Having a separate instance of gdb for
> each processor would make the problem straight forward.
>
> c) each processor has its own breakpoints, registers, PC, etc. We can
> stop each independently of each other.
>
> So... how do you suggest we handle this in Eclipse ? My first
> inclination is to run 2 simultaneous instances of it,
> although I am not
> sure that is possible. Right now it gives a workspace in use
> error.
Kim
The Eclipse debug infrastructure is entirely process and thread happy, as is the CDT which
sits on top of it. What you probably want to look at first is creating separate launches
for each of your binaries (presuming they are distinct?). Start both and you will see 2
separate process/thread hierarchies in the debug view and you can control them by making
sure the one you care about is active. Views like variables, registers etc. also depend on
debug view context and should do the right thing. You can experiment with this on your
host (linux, windoze etc) by building multiple binaries and launching them so you have
multiple debug sessions in a single eclipse.
Once you want to start synchronizing things you may have a bit more work to do - things
like startup sequence, processor synchronization etc. You can see the challenges there by
running a pair of gdb's from the command line ... one proc may break and cause the other
proc to stall, and thus the other gdb to "hang" ... then you have to signal the hung gdb
to get control of it. If you want to go there you will have to consider catching debug
events inside eclipse so you can send signals to the other gdb so eclipse can talk to it.
PMac
