This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: add-inferior / clone-inferior
- From: David Taylor <dtaylor at emc dot com>
- To: "lgustavo at codesourcery dot com" <lgustavo at codesourcery dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Mon, 20 May 2013 11:46:07 -0400
- Subject: Re: add-inferior / clone-inferior
- References: <7249 dot 1369061005 at usendtaylorx2l> <519A3BE7 dot 6010004 at codesourcery dot com>
Luis Machado <lgustavo@codesourcery.com> wrote:
> This is expected since you can actually have two inferiors, but you are
> only allowed to connect to a single remote target at one time.
>
> What would've worked is first connecting to a remote target in
> *extended* remote mode. Then you would be able to attach to more than a
> process at a time, or start more than a process at a time.
>
> By using "target remote", you're really trying to debug an already
> active process running on a remote system.
>
> I'd suggest reading about the extended remote mode. That looks like what
> you want, though multiprocess support is still a WIP.
Actually, no. The issue is not extended-remote vs remote. We have boxes
with multiple boards each running a kernel. The box I tried running gdb
against on Thursday has 10 boards of interest. Each running its own
instance of the kernel -- 2 instances each of 5 different versions of
the kernel.
For that machine if I want to talk to all 10 boards, then I need 10
different tcp connections -- each talking to a different gdb stub.