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 18:50:00 -0000 [thread overview]
Message-ID: <87k3mqhmsn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <8702.1369246895@usendtaylorx2l> (David Taylor's message of "Wed, 22 May 2013 14:21:35 -0400")
Tom> One that comes to mind is what target is associated with an inferior
Tom> created with add-inferior? How could you change this inferior's target
Tom> to connect it to some existing target?
David> Perhaps I misunderstand the question. Initially, there is just a dummy
David> target.
David> Do a command like 'file' and you have an exec target.
David> Do a command like 'run' or 'attach' or 'target remote' or 'target
David> extended-remote' and your process stratum target is pushed on top of the
David> old file stratum target.
David> Do a command like 'kill' or 'detach' and your process stratum target is
David> popped and you are back at the exec stratum target -- the exec file --
David> at the top of your target stack.
I was thinking of a scenario like: I have an existing connection to an
extended-remote target, then I want to add an inferior and then run it
on that target.
I guess something like this would work if "target extended-remote"
always did connection sharing:
add-inferior -exec whatever
target extended-remote server:port
run
The issue I have is differentiating this from the scenario of: add
inferior, connect for the first time, then try to run. Won't this do
something different if the remote is already running?
I feel like I'm confused somehow.
David> . you want to know the full set of inferiors and their targets.
David> Seems somewhat esoteric. Perhaps a maint command would be appropriate?
I suppose we could just print it in "info inferiors".
Tom
next prev parent reply other threads:[~2013-05-22 18:50 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 [this message]
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=87k3mqhmsn.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