Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: gdb@sourceware.org
Subject: RE: Who uses gdbreplay?
Date: Thu, 12 Jun 2008 19:44:00 -0000	[thread overview]
Message-ID: <1213299817.3601.686.camel@localhost.localdomain> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA042911BF@ecamlmw720.eamcs.ericsson.se>

On Thu, 2008-06-12 at 15:28 -0400, Marc Khouzam 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...   ;-)
> 
> A couple of years ago, you had posted a proposal about a gdb interface
> for reverse debugging
> http://sourceware.org/ml/gdb/2006-01/msg00013.html
> 
> I guess this did not make it to GDB?

Not to the main trunk, but it's preserved on a branch.
I'm currently creating a new updated branch, with the
eventual idea of working it into the trunk.

> Am I correct to understand that the efforts for GDB Reverse debugging
> are currently focused on teawater's GDB Record patch, which you guys 
> are helping with?

Not quite... Teawater's excellent efforts are prompting me
to revive this older work, and attempt to merge the two,
preserving the best elements of each.

But I would like to keep this thread focused on gdbreplay
as much as possible.

> To be honnest, I didn't look at the details of that patch (much too low
> level for me).  However, I was wondering if it considers reverse debugging 
> with a target (gdbserver or other stub?)  From what I understand, 
> GDB Record, will record register and memory changes as they are made.  
> For some targets, storing all this may be prohibitive.
> I wondered if the recording is done by GDB on the host instead?

That is in fact how gdbreplay works.  The log is recorded
by gdb on the host side.  Playback is done entirely on the
host side, with no participation by the target (although 
to gdb it looks like the playback is coming from the remote
target over a socket).






      reply	other threads:[~2008-06-12 19:44 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
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 [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=1213299817.3601.686.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --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