From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org, pedro@codesourcery.com
Subject: Re: NEWS entries
Date: Tue, 07 Jul 2009 19:23:00 -0000 [thread overview]
Message-ID: <83tz1oz4aw.fsf@gnu.org> (raw)
In-Reply-To: <20090707155225.GA24199@caradoc.them.org>
> Date: Tue, 7 Jul 2009 11:52:29 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, Pedro Alves <pedro@codesourcery.com>
>
> * Process record and replay
>
> In a architecture environment that supports ``process record and
> replay'', ``process record and replay'' target can record a log of
> the process execution, and replay it with both forward and reverse
> execute commands.
>
> I believe this is currently only supported on i386-linux, is that right?
> If so, we should say so. Also, "execution commands".
>
> set non-stop
> show non-stop
> Control whether other threads are stopped or not when some thread hits
> a breakpoint.
>
> Documenting "set non-stop" is fine - but can we get some text about
> non-stop mode, itself? As above, this should include which platforms
> non-stop is initially supported on.
You are right on both counts. Patches are welcome, or I will do it
eventually.
prev parent reply other threads:[~2009-07-07 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 15:52 Daniel Jacobowitz
2009-07-07 16:09 ` Pedro Alves
2009-07-07 19:23 ` Eli Zaretskii [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=83tz1oz4aw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.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