From: Tom Tromey <tromey@redhat.com>
To: David Taylor <dtaylor@emc.com>
Cc: gdb@sourceware.org
Subject: Re: add-inferior / clone-inferior
Date: Wed, 22 May 2013 14:47:00 -0000 [thread overview]
Message-ID: <87ehczhy0c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87bo84l5ad.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 21 May 2013 09:30:02 -0600")
Tom> The whole target stack needs to be switched out depending on which
Tom> target is "active". I guess one idea would be to make it depend on the
Tom> current inferior. But then I would worry whether the correct inferior
Tom> is always selected when gdb is doing various operations.
Thinking about it some more, it may be simpler to associate the target
stack with a program space, not an inferior. This will have the same
effect, but I think gdb is generally more careful about selecting a
program space before doing an operation. E.g., linespec already does
this properly, breakpoints already do this properly, etc.
Tom> I wonder if there are other UI issues to consider.
One that comes to mind is what target is associated with an inferior
created with add-inferior? How could you change this inferior's target
to connect it to some existing target?
Also, some way to see the active targets would be needed. "info target"
already seems to be taken.
Tom
next prev parent reply other threads:[~2013-05-22 14:47 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 [this message]
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=87ehczhy0c.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