From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Hui Zhu" <teawater@gmail.com>, <gdb-patches@sourceware.org>
Cc: "Pedro Alves" <pedro@codesourcery.com>,
"Michael Snyder" <msnyder@vmware.com>,
"Thiago Jung Bauermann" <bauerman@br.ibm.com>,
"Eli Zaretskii" <eliz@gnu.org>,
"Mark Kettenis" <mark.kettenis@xs4all.nl>
Subject: RE: Process record and replay checked in to main trunk
Date: Thu, 30 Apr 2009 14:43:00 -0000 [thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA075CA8EE@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <daef60380904300059g191dfe0bu7773ee01f35892bf@mail.gmail.com>
> Process record and replay make gdb can record inferior execute log and
> replay (include reverse debug).
> Now, it support I386-Linux single-thread single-inferior native debug.
>
> It was checked in today.
Congratulations!
I've checked-out the new HEAD and running PRecord in Eclipse
with no patches.
> Guys, please work on it if you interesting with some of them. And
> feel free tell me your ideas and comments. It will help precord a
> lot.
Here are some things I think would be nice:
1- The handling of queries in PRecord as we discussed in
http://sourceware.org/ml/gdb/2009-03/msg00194.html
2- speed (but you already mentioned you will work on this)
3- Some MI support
- 'record' and 'stoprecord' could have an MI equivalent
- trying to get the MI commands for Reverse debugging done
- *stopped MI event could/should have a special 'reason' field
when
it is triggered because Replay execution is finished.
Currently, there is no 'reason' field in this case.
Having the 'reason' field would allow a fronten to optionally
resume the execution at that point, instead of mysteriously
stopping when the Replay execution is finished.
I'm sure more suggestion will arise as people start using it.
Again, good work!
Marc
next prev parent reply other threads:[~2009-04-30 14:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 7:59 Hui Zhu
2009-04-30 14:43 ` Marc Khouzam [this message]
2009-04-30 20:00 ` Michael Snyder
2009-05-01 9:16 ` Eli Zaretskii
2009-05-01 17:02 ` Hui Zhu
2009-05-01 17:55 ` Eli Zaretskii
2009-05-03 14:15 ` Hui Zhu
2009-05-04 11:17 ` Eli Zaretskii
2009-05-04 16:46 ` Michael Snyder
2009-05-05 13:48 ` Hui Zhu
2009-05-04 14:32 ` Marc Khouzam
2009-05-04 16:46 ` Eli Zaretskii
2009-05-05 14:11 ` Hui Zhu
2009-05-01 9:26 ` Eli Zaretskii
2009-05-01 17:08 ` Hui Zhu
2009-05-01 17:58 ` Eli Zaretskii
2009-05-01 13:28 ` Eli Zaretskii
2009-05-03 13:54 ` Hui Zhu
2009-05-04 11:15 ` Eli Zaretskii
2009-05-05 13:40 ` Hui Zhu
2009-05-05 19:01 ` Eli Zaretskii
2009-05-05 19:32 ` Mark Kettenis
2009-05-05 19:52 ` Eli Zaretskii
2009-05-06 13:34 ` Hui Zhu
[not found] ` <daef60380904300102o4470ac45he41f6b72176b1947@mail.gmail.com>
2009-05-07 22:24 ` Pierre Muller
2009-05-07 22:52 ` Michael Snyder
2009-05-07 23:05 ` Pedro Alves
2009-05-08 5:12 ` Hui Zhu
2009-05-08 12:11 ` Pierre Muller
2009-05-10 17:28 ` Hui Zhu
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=6D19CA8D71C89C43A057926FE0D4ADAA075CA8EE@ecamlmw720.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.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