From: Tom Tromey <tromey@redhat.com>
To: David Taylor <dtaylor@emc.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: add-inferior / clone-inferior
Date: Wed, 22 May 2013 20:21:00 -0000 [thread overview]
Message-ID: <87sj1eg40a.fsf@fleche.redhat.com> (raw)
In-Reply-To: <9342.1369251736@usendtaylorx2l> (David Taylor's message of "Wed, 22 May 2013 15:42:16 -0400")
David> I wasn't thinking about that scenario. My current interest is talking
David> to the kernel of a machine that might be in a local lab or might be at a
David> customer site half way around the world.
Yeah.
I'm just brainstorming different scenarios to try to understand what
problems multi-target might have. Running a new program via an
extended-remote gdbserver seems like a reasonable thing to want to do;
but I wasn't sure of the mechanics.
David> But, if you give it a different server:port than previously, presumably
David> you want it to open a new connection. I think it needs to be clear to
David> the user whether it is reusing an existing connection or creating a new
David> one. Perhaps a different syntax than server:port when reusing a
David> connection?
Yeah, that may be the way to go.
Or maybe "always reuse" is best? Since it seems unlikely to want to
open multiple concurrent connections to the exact same server/port pair.
(I guess it could work with some hypothetical gdbserver. But I don't
think it exists.)
David> If we just printed the top stratum element putting it into info
David> inferiors is probably reasonable. If it was more verbose, I don't think
David> the average user would care to see it.
I was just thinking something like:
(gdb) info inferior
Num Description Executable Target
* 1 process 2994 /usr/bin/gdb native
2 process 1222 /bin/sh server:9999
David> I'd also like a name field somewhere for the inferior. I can envision
David> debugging a client server problem by having both under one GDB rather
David> than two GDBs. Ideally, names that the 'inferior' command recognizes
David> in addition to a numeric inferior id. Then I could do
David> inferior client
David> ... some commands ...
David> inferior server
David> ... some commands ...
IT sets were the answer to this in the past, but I see in your other
mail that you also wanted it to show up in "info inferiors". That seems
reasonable to me; though maybe it could be some kind of itset flag.
I think Pedro and Yao have the best status on itsets.
Tom
next prev parent reply other threads:[~2013-05-22 20:21 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
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 [this message]
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=87sj1eg40a.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dtaylor@emc.com \
--cc=gdb@sourceware.org \
/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