From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@specifix.com>
Cc: gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] gdbreplay V2.0
Date: Fri, 04 Jul 2008 11:07:00 -0000 [thread overview]
Message-ID: <uabgx29is.fsf@gnu.org> (raw)
In-Reply-To: <1215020939.3601.1594.camel@localhost.localdomain>
> From: Michael Snyder <msnyder@specifix.com>
> Cc: gdb-patches@sourceware.org
> Date: Wed, 02 Jul 2008 10:48:59 -0700
>
> +* New and improved debug session record and replay
> +
> +There is now a new and improved version of the 'gdbreplay' utility
> +called 'gdb-freeplay'. It makes use of the same remote protocol
> +log files ("set remotelogfile <filename>"), but allows a great deal
> +more flexibility while playing the logs back.
This NEWS entry is okay, but please add something to the effect that
more details are available in gdbserver/README. (Of course, I'd
prefer a section in the manual...)
next prev parent reply other threads:[~2008-07-04 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 4:50 Michael Snyder
2008-07-02 17:50 ` Michael Snyder
2008-07-04 11:07 ` Eli Zaretskii [this message]
2008-07-03 1:56 ` teawater
2008-07-03 2:50 ` Michael Snyder
2008-07-04 10:53 ` Eli Zaretskii
2008-07-08 3:34 ` Michael Snyder
2008-07-14 22:29 ` Eli Zaretskii
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=uabgx29is.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=msnyder@specifix.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