Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Mon, 14 Jul 2008 22:29:00 -0000	[thread overview]
Message-ID: <E1KIWWi-0006eO-3A@fencepost.gnu.org> (raw)
In-Reply-To: <1215488044.3549.116.camel@localhost.localdomain> (message from 	Michael Snyder on Mon, 07 Jul 2008 20:34:04 -0700)

> From: Michael Snyder <msnyder@specifix.com>
> Cc: gdb@sourceware.org, gdb-patches@sourceware.org
> Date: Mon, 07 Jul 2008 20:34:04 -0700

Sorry for the delay.  I'm traveling with low connectivity and very
little time for catching up.

> On Fri, 2008-07-04 at 13:52 +0300, Eli Zaretskii wrote:
> > > From: Michael Snyder <msnyder@specifix.com>
> > > Date: Tue, 01 Jul 2008 21:49:18 -0700
> > > 
> > > Here's a new contribution -- I call it gdb-freeplay, an 
> > > improved and less restrictive version of gdbreplay.  Its
> > > something I've been playing around with for some time now.
> > 
> > Thanks!
> > 
> > What, nothing for the manual?
> 
> Well... er... the manual doesn't mention the old gdbreplay...

Yes, I know.

> But I don't mind writing something.  It's a deal more complex
> than the old one.  Where do you think it would fit in?

I think it should be a separate chapter.


      reply	other threads:[~2008-07-14 22:29 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
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 [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=E1KIWWi-0006eO-3A@fencepost.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