From: "Jakob Engblom" <jakob@virtutech.com>
To: "'Marc Khouzam'" <marc.khouzam@ericsson.com>,
"'Hui Zhu'" <teawater@gmail.com>
Cc: "'Michael Snyder'" <msnyder@vmware.com>, <gdb@sourceware.org>
Subject: RE: [FYI] tutorial for process record and reverse debugging
Date: Mon, 26 Oct 2009 07:58:00 -0000 [thread overview]
Message-ID: <009c01ca5611$8c520a20$a4f61e60$@com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC5157A95F8B@EUSAACMS0703.eamcs.ericsson.se>
> If going straight to the end of the recording log is a valuable
> feature, I was thinking it may deserve its own command.
>
> Ultimately, I'm hoping that with such a command, we can then see
> if we can have PRecord directly jump from recorded execution
> to live execution without stopping.
Note that we had a discussion a while ago about adding a general "go to point in
time in recording/reverse execution history" command, which would kind of solve
this as a special case (provided you can find the "last" time). We can already
do this in Simics, but there is no support in the gdb-serial protocol or the gdb
CLI or MI to access the function. The undodb people had the same issue.
/jakob
next prev parent reply other threads:[~2009-10-26 7:54 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
2009-10-26 7:54 ` Hui Zhu
2009-10-26 8:06 ` Jakob Engblom
2009-10-26 7:58 ` Jakob Engblom [this message]
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='009c01ca5611$8c520a20$a4f61e60$@com' \
--to=jakob@virtutech.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--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