From: Doug Evans <dje@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: Move the multi-forks support to the generic multi-inferiors support.
Date: Sun, 31 May 2009 22:23:00 -0000 [thread overview]
Message-ID: <e394668d0905311518j4177db18o2f8c52c7edf035be@mail.gmail.com> (raw)
In-Reply-To: <200905312308.04692.pedro@codesourcery.com>
On Sun, May 31, 2009 at 3:08 PM, Pedro Alves <pedro@codesourcery.com> wrote:
>> I guess "info inferiors" would show all the checkpointed forks for a
>> given inferior?
>
> That's one option, sure. I haven't given much attention to user
> interface details of checkpoints. Another idea we be to just flag that
> there are checkpoints available, and then the user can do the usual
> "info checkpoints" to see them. This avoids having a too crowded
> "info inferiors" output.
Other targets (e.g. simulators) may have checkpoints that have nothing
to do with multiple inferiors, so fwiw I think they should be kept
separate.
next prev parent reply other threads:[~2009-05-31 22:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 23:13 Pedro Alves
2009-05-31 20:46 ` Tom Tromey
2009-05-31 22:07 ` Pedro Alves
2009-05-31 22:23 ` Doug Evans [this message]
2009-06-01 15:58 ` Tom Tromey
2009-06-06 0:09 ` Tom Tromey
2009-06-06 16:06 ` Pedro Alves
2009-06-08 1:34 ` Marc Khouzam
2009-06-08 22:43 ` Tom Tromey
2009-06-08 23:22 ` Pedro Alves
2009-06-08 22:39 ` Tom Tromey
2009-06-08 23:16 ` Pedro Alves
2009-06-10 22:09 ` Tom Tromey
2009-06-10 22:13 ` Pedro Alves
2009-06-08 12:58 ` Pedro Alves
2009-06-11 19:32 ` Michael Snyder
2009-07-01 18:27 ` Pedro Alves
2009-07-01 19:16 ` Eli Zaretskii
2009-07-02 14:32 ` Pedro Alves
2009-07-02 19:00 ` Eli Zaretskii
2009-07-02 21:59 ` Pedro Alves
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=e394668d0905311518j4177db18o2f8c52c7edf035be@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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