From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb ml <gdb@sourceware.org>, Pedro Alves <pedro@codesourcery.com>,
Marc Khouzam <marc.khouzam@ericsson.com>,
Michael Snyder <msnyder@vmware.com>,
Eli Zaretskii <eliz@gnu.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: Process record and replay checked in to main trunk
Date: Sat, 02 May 2009 01:57:00 -0000 [thread overview]
Message-ID: <1241229412.8130.10.camel@localhost.localdomain> (raw)
In-Reply-To: <daef60380904300102o4470ac45he41f6b72176b1947@mail.gmail.com>
Hi Hui,
El jue, 30-04-2009 a las 16:02 +0800, Hui Zhu escribió:
> It was checked in today.
> Thanks for evey people that spent time on process record. Precord
> can't be a part of gdb without your help. Thank you very much. :)
Congratulations! And thanks for your perseverance in getting this
functionality accepted! It was certainly no easy task, unfortunately.
My only regret is not having helped you more with this (in fact, I only
helped a little bit). For better or worse, all my GDB-related energy has
been directed to getting the Python branch merged in...
> And precord still has a long way to go. There have a lot of thing need to do:
Thanks for this road map. IMHO this is the kind of thing that could go
on the wiki. In fact, I just added it under:
http://sourceware.org/gdb/wiki/ReversibleDebugging
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-05-02 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <daef60380904300059g191dfe0bu7773ee01f35892bf@mail.gmail.com>
2009-04-30 14:51 ` Hui Zhu
2009-05-02 1:57 ` Thiago Jung Bauermann [this message]
2009-05-03 15:54 ` Hui Zhu
2009-05-05 17:07 paawan oza
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=1241229412.8130.10.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--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