From: "Eli Zaretskii" <eliz@gnu.org>
To: fche@redhat.com, dan@shearer.org, gdb@sources.redhat.com
Subject: Re: [discuss] Support for reverse-execution
Date: Sat, 21 May 2005 15:46:00 -0000 [thread overview]
Message-ID: <01c55e1b$Blat.v2.4$99652dc0@zahav.net.il> (raw)
In-Reply-To: <20050521141931.GA430@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 21 May 2005 10:19:31 -0400)
> Date: Sat, 21 May 2005 10:19:31 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: fche@redhat.com, dan@shearer.org, gdb@sources.redhat.com
>
> One, it requires extensive additional support from the target. State
> is huge and complicated - multiple threads, file system operations,
> network packets. You need a target that supports checkpointing to do
> this. I'm told there are native platforms which could offer this - I
> just don't know what any of them are.
Well, at least the Linux kernel developers could perhaps be persuaded
to add such a support.
> Two, this is basically the same thing as the bookmarking feature
> already proposed in this thread; just have GDB automatically take a
> bookmark at every stop.
Correct. What I'm saying is that by adding this we would provide a
large part of user-level functionality that is served by the full set
of reverse-* commands, but with the advantages that:
(a) the list of new commands is much smaller and thus simpler
(b) we don't need to figure out the right semantics of tricky
commands like "reverse-next" and "reverse-finish"
(c) part of the implementation is on the GDB side (as opoosed to the
target side), so it will be easier to enable it for more targets
> > If we implement something like that, perhaps we could ditch all the
> > reverse-* commands whose names we are discussing at such length in
> > this thread, and instead implement only one command, called, say,
> > "rewind" or "backup" or some such. That, and a set/show mode command
> > to enable checkpointing would be enough, I think, to have 99% of the
> > functionality originally suggested in this thread.
>
> Not at all. Here's a big use of reversible debugging: timing-sensitive
> or otherwise very hard-to-reproduce problems. You want to be able to
> leave the program running, hooked up to a simulator and a debugger, and
> then once the mysterious bug has occurred back up a little bit to see
> why.
Okay so perhaps it's less than 99%, but it's still a large portion.
next prev parent reply other threads:[~2005-05-21 15:46 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 17:47 Dan Shearer
2005-05-16 18:04 ` Dan Shearer
2005-05-20 18:15 ` Daniel Jacobowitz
2005-05-21 0:05 ` Frank Ch. Eigler
2005-05-21 10:13 ` Eli Zaretskii
2005-05-21 10:28 ` Russell Shaw
2005-05-21 12:38 ` Eli Zaretskii
2005-05-21 12:55 ` Russell Shaw
2005-05-21 14:39 ` Russell Shaw
2005-05-21 14:19 ` Daniel Jacobowitz
2005-05-21 15:46 ` Eli Zaretskii [this message]
2005-05-21 17:43 ` Daniel Jacobowitz
2005-05-23 19:39 ` Dan Shearer
-- strict thread matches above, loose matches on Subject: below --
2005-05-21 15:53 Paul Schlie
2005-05-20 22:11 Michael Snyder
2005-05-20 23:32 ` Paul Schlie
2005-05-20 21:59 Michael Snyder
2005-05-20 21:51 Michael Snyder
2005-05-21 9:44 ` Eli Zaretskii
2005-05-20 21:44 Michael Snyder
2005-05-20 21:25 Michael Snyder
2005-05-20 21:16 Michael Snyder
2005-05-20 21:31 ` Daniel Jacobowitz
2005-05-21 9:39 ` Eli Zaretskii
2005-05-23 18:19 ` Michael Snyder
2005-05-20 21:11 Michael Snyder
2005-05-20 21:27 ` Daniel Jacobowitz
2005-05-20 19:02 Michael Snyder
2005-05-20 20:43 ` Eli Zaretskii
2005-05-20 21:03 ` Michael Snyder
2005-05-20 15:49 Paul Schlie
2005-05-20 17:41 ` Dan Shearer
2005-05-20 22:01 ` Paul Schlie
2005-05-20 22:08 ` Daniel Jacobowitz
2005-05-20 22:43 ` Paul Schlie
2005-05-21 0:58 ` Daniel Jacobowitz
2005-05-21 1:42 ` Paul Schlie
2005-05-21 1:53 ` Daniel Jacobowitz
2005-05-21 1:56 ` Daniel Jacobowitz
2005-05-21 15:03 ` Paul Schlie
2005-05-21 14:13 ` Paul Schlie
2005-05-21 14:23 ` Daniel Jacobowitz
2005-05-21 15:04 ` Paul Schlie
2005-05-20 20:58 ` Michael Snyder
2005-05-20 21:35 ` Paul Schlie
2005-05-19 1:23 Dan Shearer
2005-05-19 13:01 ` Johan Rydberg
2005-05-19 13:18 ` Daniel Jacobowitz
2005-05-19 13:47 ` Johan Rydberg
2005-05-20 10:37 ` Eli Zaretskii
2005-05-20 11:37 ` Andreas Schwab
2005-05-20 13:18 ` Daniel Jacobowitz
2005-05-20 13:36 ` Fabian Cenedese
2005-05-20 13:47 ` Daniel Jacobowitz
2005-05-20 14:41 ` Eli Zaretskii
2005-05-20 22:14 ` Daniel Jacobowitz
2005-05-20 12:22 ` Johan Rydberg
2005-05-20 13:19 ` Daniel Jacobowitz
2005-05-20 14:12 ` Eli Zaretskii
2005-05-20 13:14 ` Daniel Jacobowitz
2005-05-20 14:34 ` Eli Zaretskii
2005-05-20 15:40 ` Johan Rydberg
2005-05-20 10:47 ` Eli Zaretskii
2005-05-12 23:08 Michael Snyder
2005-05-13 6:23 ` Eli Zaretskii
2005-05-19 13:46 ` Daniel Jacobowitz
2005-05-19 18:46 ` Michael Snyder
2005-05-19 19:26 ` Johan Rydberg
2005-05-20 10:55 ` Eli Zaretskii
2005-05-20 13:04 ` Daniel Jacobowitz
2005-05-20 14:30 ` Eli Zaretskii
2005-05-20 14:43 ` Andreas Schwab
2005-05-20 20:48 ` Michael Snyder
2005-05-20 20:51 ` Daniel Jacobowitz
2005-05-20 20:38 ` Michael Snyder
2005-05-20 15:05 ` Vladimir Prus
2005-05-20 15:58 ` Eli Zaretskii
2005-05-20 18:14 ` Daniel Jacobowitz
2005-05-20 18:30 ` Eli Zaretskii
2005-05-20 19:27 ` Stan Shebs
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='01c55e1b$Blat.v2.4$99652dc0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=dan@shearer.org \
--cc=fche@redhat.com \
--cc=gdb@sources.redhat.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