From: Michael Snyder <msnyder@vmware.com>
To: gdb@sourceware.org
Subject: real world reverse debugging success story
Date: Thu, 12 Nov 2009 01:09:00 -0000 [thread overview]
Message-ID: <4AFB54CA.9090900@vmware.com> (raw)
Hey guys,
Just wanted to make note that I used reverse debugging to
solve a real world gdb bug (the recently submitted one for
dcache.c).
First I found where the lists were cross-linked, then I put
watchpoints on the list elements that were crossed, and ran
backwards. One watchpoint took me to dcache_alloc, and the
other to dcache_invalidate.
Then I used some bookmarks to look at the state of the list
before and after, and close in on the actual problem (which
was in fact in another function).
Doug rewrote my patch (thanks Doug), but he verified that
the actual bug was exactly what process record revealed it
to be.
Whee!
Michael
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.
next reply other threads:[~2009-11-12 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 1:09 Michael Snyder [this message]
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
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=4AFB54CA.9090900@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
/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