From: Michael Snyder <msnyder@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>, gdb@sourceware.org
Subject: Re: Who uses gdbreplay?
Date: Thu, 12 Jun 2008 19:39:00 -0000 [thread overview]
Message-ID: <1213299561.3601.681.camel@localhost.localdomain> (raw)
In-Reply-To: <20080612191849.GA3704@caradoc.them.org>
On Thu, 2008-06-12 at 15:18 -0400, Daniel Jacobowitz wrote:
> On Thu, Jun 12, 2008 at 12:12:01PM -0700, Michael Snyder wrote:
> > > This very morning, I was asked if GDB had any kind of foundation for reverse
> > > debugging on a target. Is gdbreplay what I am looking for?
> >
> > Not yet... ;-)
>
> So... what will the resulting program have in relation to the existing
> gdbreplay? It sounds like not much at all.
Well I don't want to promise too much too early, but
what I have in mind will be VERY different from the
current gdbreplay.
Rather than requiring you to give exactly the same sequence
of gdb commands as during the recording, it will allow you to
"step" forward (and eventually backward) thru the log, and pause
to examine arbitrary state and issue arbitrary commands at any
point along the way. Of course, you can only examine state that
was saved during the recording session.
In that sense, it will somewhat resemble tracepoint debugging.
In fact, I may be able to allow the "tfind" tracepoint commands
to work, which would allow you to "skip ahead" (or backward)
to an arbitrary point in the log.
next prev parent reply other threads:[~2008-06-12 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 18:35 Michael Snyder
2008-06-12 18:55 ` Marc Khouzam
2008-06-12 19:07 ` Daniel Jacobowitz
2008-06-12 19:12 ` Michael Snyder
2008-06-12 19:19 ` Daniel Jacobowitz
2008-06-12 19:39 ` Michael Snyder [this message]
2008-06-12 19:47 ` Daniel Jacobowitz
2008-06-12 19:57 ` Michael Snyder
2008-06-12 20:06 ` Daniel Jacobowitz
2008-06-12 20:15 ` Michael Snyder
2008-06-12 20:24 ` Daniel Jacobowitz
2008-06-12 20:56 ` Michael Snyder
2008-06-12 19:28 ` Marc Khouzam
2008-06-12 19:44 ` Michael Snyder
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=1213299561.3601.681.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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