From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Michael Snyder'" <msnyder@vmware.com>
Cc: "'Hui Zhu'" <teawater@gmail.com>,
"'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: RE: [FYI] tutorial for process record and reverse debugging
Date: Wed, 21 Oct 2009 15:06:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC5157AEC0A5@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <4ADE1824.8090701@vmware.com>
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Michael Snyder
> Sent: Tuesday, October 20, 2009 4:06 PM
> To: Marc Khouzam
> Cc: 'Hui Zhu'; 'gdb@sourceware.org'
> Subject: Re: [FYI] tutorial for process record and reverse debugging
>
> [...]
> > Now, let me describe the case I am imagining.
> > It is as simple as it gets.
> > The user simply enables the 'reverse debugging' feature.
> > After that, the user should not need to pay attention to
> > record logs and such. What they should see is that they
> > can go forward or backwards as if everything was true 'execution'.
> > We don't need to differentiate between 'execution' and 'replay'.
> >
> > For example, when changing memory, the user doesn't need to know
> > that we are moving away from replay into a new execution. All
> > they see is that the program moves forward with the new memory
> > value.
> >
> > And that is why, in this scenario, I thought it seemed
> > unintuitive to stop execution when
> > arriving at the end of the replay log; instead, the user
> > pressed 'continue' and the 'execution' should continue until
> > a breakpoint or the end of the program, as if a true execution.
> >
> > The only limitation to this, is that we cannot go backwards
> > past the start of the recording. But I think this can be easily
> > understood by the user.
> >
> > I don't think this scenario is good for everyone, but I think
> > for average users, it makes reverse debugging very fluid.
>
> I think that's a great scenario -- just not the only scenario.
> We could call that Marc-mode, for devel purposes. ;-)
Just so it doesn't go to my head, how about "auto-mode"
as in "transitions from replay to record are done automatically"
(and without querying the user).
> How would you suggest we might turn on Marc-mode with a
> single command?
Maybe we can introduce a user setting such as
"record mode <auto|someothermode>"
> Or do you imagine it being the default?
Greg's follow-up email made me re-think a bit how intuitive
auto-mode would be. I'll reply to his email with my comments.
Marc
next prev parent reply other threads:[~2009-10-21 14:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 23:48 Michael Snyder
2009-10-19 12:36 ` Hui Zhu
2009-10-19 12:57 ` Marc Khouzam
2009-10-19 13:06 ` Hui Zhu
2009-10-19 13:20 ` Marc Khouzam
2009-10-19 16:35 ` Hui Zhu
2009-10-20 0:59 ` Michael Snyder
2009-10-19 18:24 ` Michael Snyder
2009-10-20 6:44 ` Marc Khouzam
2009-10-20 21:01 ` Michael Snyder
2009-10-21 5:16 ` Greg Law
2009-10-21 15:40 ` Marc Khouzam
2009-10-24 19:29 ` Greg Law
2009-10-25 2:01 ` Michael Snyder
2009-10-26 3:05 ` Marc Khouzam
2009-10-26 9:59 ` Jakob Engblom
2009-10-22 6:31 ` Michael Snyder
2009-10-21 15:06 ` Marc Khouzam [this message]
2009-10-26 7:54 ` Hui Zhu
2009-10-26 8:06 ` Jakob Engblom
2009-10-26 7:58 ` Jakob Engblom
2009-10-26 19:10 ` Michael Snyder
2009-10-27 18:32 ` Jakob Engblom
2009-10-19 18:23 ` Michael Snyder
2009-10-26 3:12 ` Hui Zhu
2009-10-26 8:02 ` Jakob Engblom
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=F7CE05678329534C957159168FA70DEC5157AEC0A5@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.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