Re: [cdt-dev] gdb multi question.

[Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>]

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schaefer, Doug
> Sent: Tuesday, January 11, 2011 3:33 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] gdb multi question.
> 
> Just diving into the multi-inferior stuff with gdb. I haven't 
> seen documented anywhere on how to hook gdb up to multiple 
> remote targets. I figured I could just add-inferior, switch 
> to it, and then do another target remote but that just wanted 
> to kill my first target remote. This was with 7.1 on Fedora 13.
> 
> I know we have some experts on this list :). Am I missing something?

The support for multi-process is being added to HEAD gradually.
This is the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=237306

First, you must know that you will need GDB 7.2 to do this.
Although GDB 7.1 would have been sufficient, it didn't have the
proper MI commands yet, so we did the work for GDB 7.2.

What is already available is to attach to multiple processes using
a local attach session.

Breakpoints are not properly working yet, but Onur posted a patch 
recently, which I'm hoping to look at in the coming few days.

So, launch a local attach session and press the green connect
button in the debug view to keep attaching to new processes.
Those processes have to be running already.

To get a remote attach session we are just missing a prompt to ask
the user where the binary file is.  GDB can 'guess' the location for
a local attach session, but not a remote one.  This prompt brings up
again the question of how to handle the UI for such cases.  I liked 
the idea of using different launches as EDC does, but I'm not sure 
how that is going to feel.  I have an entry on my TODO list to
prototype it, but I don't know when I'll find the time.

Having your opinions on usability will greatly help get this
finalized.

Marc