From: Tom Tromey <tromey@redhat.com>
To: David Taylor <dtaylor@emc.com>
Cc: gdb@sourceware.org
Subject: Re: add-inferior / clone-inferior
Date: Mon, 24 Jun 2013 20:50:00 -0000 [thread overview]
Message-ID: <878v1zutb9.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.
Tom> I think I'd also examine all the calls to push_target, unpush_target,
Tom> and target_is_pushed to make sure they are ok. I think there are hidden
Tom> gotchas here. E.g., "record" will eventually call push_target via
Tom> record_full_open -- which examines the current target stack and stores
Tom> stuff into a global.
I played with this a bit last week and again today.
I have it working well enough that I can run one inferior while visiting
a core file in another.
I'll push my branch eventually; sooner if somebody wants to see it.
Tom> I wonder if there are other UI issues to consider.
Pedro pointed out a few on irc.
They're in the notes on the branch.
Tom> It would be very nice to have a wiki page for this project, with the
Tom> plans and links.
I'll set one up.
Tom
prev parent reply other threads:[~2013-06-24 20: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
2013-05-22 19:42 ` David Taylor
2013-05-22 20:21 ` Tom Tromey
2013-06-24 20:50 ` Tom Tromey [this message]
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=878v1zutb9.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