Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Marc Khouzam <marc.khouzam@ericsson.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: real world reverse debugging success story
Date: Thu, 12 Nov 2009 21:07:00 -0000	[thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC5158E83B5E@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <4AFB5FDD.7010008@vmware.com>

 

> -----Original Message-----
> From: Michael Snyder [mailto:msnyder@vmware.com] 
> Sent: November-11-09 8:08 PM
> To: Michael Snyder
> Cc: Marc Khouzam; gdb@sourceware.org
> Subject: Re: real world reverse debugging success story
> 
> Michael Snyder wrote:
> > Marc Khouzam wrote:
> >> [...]
> >>> Stats: used an 8 million instruction cache, running as a
> >>> ring buffer.  Had to record over 80 million instructions
> >>> before I tripped the bug.  Saved core file with record log
> >>> was 250 megabytes, and reloaded fine.
> >> Very impressive!
> >>
> >> How was the responsiveness?  I assume you didn't step
> >> over all those instuctions ;-)  So, you must have run the program
> >> and have it be recorded for a while.  I'm wondering if the 
> execution
> >> was annoyingly slow, or if it was ok.
> > 
> > The record phase was kind of slow, but I'm sure that was
> > impacted by a very large number of notifications to the effect
> > that process record would not record some memory because it
> > could not get the segment register.
> > 
> > Replay was not bad at all, about 15 seconds to get from
> > "goto-bookmark begin" to "goto-bookmark end".  For 80
> > million instructions, that's about 5 million insns / sec.

You know what, it just dawned on me that I never really payed
attention to the replaying spead :-O  I'm glad to hear it is good.

It is really the recording speed that I'm curious about.  I think
right now, this is a big limiting factor (understandably of course),
that would prevent the use of PRecord for real world applications.

I've had one person want to use PRecord to learn about a piece
of software.  They figured that they would record execution up to
a point in the code they know would hit, and then could go backwards
to find a more proper starting point for their investigation.  But
the recording was to slow to allow the application to reach far enough
fast enough.

I was happy to see that Hui had some ideas on how to improve the
recording speed.

This reverse 'thingy' as so much potential! :-)

> > 
> > Much faster than a first gen IBM PC, for instance!   ;-)
> 
> Oh, sorry, it was 8 million insns, so about 0.5M / sec.
> 
> 


  reply	other threads:[~2009-11-12  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  1:09 Michael Snyder
2009-11-12  1:18 ` Marc Khouzam
2009-11-12  3:38   ` Michael Snyder
2009-11-12 20:53     ` Michael Snyder
2009-11-12 21:07       ` Marc Khouzam [this message]
2009-11-12 21:19     ` Sean Chen

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=F7CE05678329534C957159168FA70DEC5158E83B5E@EUSAACMS0703.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.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