From: David Taylor <dtaylor@emc.com>
To: "lgustavo@codesourcery.com" <lgustavo@codesourcery.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: add-inferior / clone-inferior
Date: Mon, 20 May 2013 15:46:00 -0000 [thread overview]
Message-ID: <7856.1369064767@usendtaylorx2l> (raw)
In-Reply-To: <519A3BE7.6010004@codesourcery.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.
next prev parent reply other threads:[~2013-05-20 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 14:43 David Taylor
2013-05-20 15:06 ` Luis Machado
2013-05-20 15:46 ` David Taylor [this message]
2013-05-20 15:52 ` Luis Machado
2013-05-21 1:01 ` Yao Qi
2013-05-21 13:15 ` David Taylor
2013-05-21 13:52 ` Tom Tromey
2013-05-21 14:35 ` David Taylor
2013-05-21 15:46 ` Tom Tromey
2013-05-22 14:47 ` Tom Tromey
2013-05-22 18:21 ` David Taylor
2013-05-22 18:50 ` Tom Tromey
2013-05-22 19:42 ` David Taylor
2013-05-22 20:21 ` Tom Tromey
2013-06-24 20:50 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7856.1369064767@usendtaylorx2l \
--to=dtaylor@emc.com \
--cc=gdb@sourceware.org \
--cc=lgustavo@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox