From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: pi3orama <pi3orama@gmail.com>
Subject: Re: ReBranch - a record-replay debugging tool
Date: Thu, 09 Jun 2011 09:27:00 -0000 [thread overview]
Message-ID: <201106091027.20575.pedro@codesourcery.com> (raw)
In-Reply-To: <4DF0748B.2060703@gmail.com>
On Thursday 09 June 2011 08:21:47, pi3orama wrote:
> Hi,
>
> I developed a new record-replay tool -- ReBranch
> (http://code.google.com/p/rebranch/), which focus on debugging
> non-deterministic bugs. ReBranch can record the outgoing addresses of
> every branch instructions, and recreate the whole control flow when
> debugging. I have use it to fix some bugs in real open source projects
> such as lighttpd and memcached. Unfortunately, few people knows this
> project at google code, so nearly no one uses it.
Nice!
>
> I know that GDB has its own record-replay. However, I still believe
> ReBranch is useful: ReBranch focus on recording in production systems,
> its record performance is better than GDB's recording, it can record
> whole program path (GDB can only record part of it), and most important,
> ReBranch can be used in multi-threading programs.
Can you outline ReBranch's record/replay strategy, and how it differs
from GDB's record?
> I send this mail because I eagerly expect people to use my tool on their
> developing process, and help me to improve it. And also, I want the
> replay tool to be more integrated with GDB -- currently ReBranch use a
> modified gdbserver to do the replay work, however, because ReBranch only
> records control-flow, the replay performance is far from prefect.
Since it based on modified gdbserver sources, making it a derivative
work, it must be GPLv3, right? I ask because the website says
MIT license.
--
Pedro Alves
next prev parent reply other threads:[~2011-06-09 9:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1307602807.17016.ezmlm@sourceware.org>
2011-06-09 7:23 ` pi3orama
2011-06-09 9:27 ` Pedro Alves [this message]
2011-06-09 10:32 ` paawan oza
2011-06-09 13:05 ` pi3orama
[not found] ` <4DF0A729.4070106@gmail.com>
2011-06-09 11:23 ` Pedro Alves
2011-06-09 12:06 ` pi3orama
[not found] <bcaec5395f2aa367da04a5462782@google.com>
2011-06-09 12:26 ` Pedro Alves
2011-06-09 12:54 ` pi3orama
2011-06-09 14:37 ` Joel Brobecker
2011-06-09 14:51 ` Pedro Alves
[not found] ` <BANLkTi=Mk0-PXb=7m0RZvEt7jegz17JXHw@mail.gmail.com>
2011-06-09 16:11 ` pi3orama
2011-06-09 16:20 ` Pedro Alves
2011-06-09 16:39 Nan Wang
2011-06-09 19:20 ` paawan oza
[not found] ` <bcaec5215b03b867ea04a5500b35@google.com>
2011-06-10 1:55 ` pi3orama
2011-06-10 8:04 ` paawan oza
2011-06-10 8:15 ` pi3orama
2011-06-10 9:14 ` paawan oza
2011-06-10 9:36 ` pi3orama
2011-06-10 5:51 ` Yao Qi
2011-06-10 6:39 ` pi3orama
2011-06-13 1:57 Robert Bu
2011-06-13 2:03 ` pi3orama
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=201106091027.20575.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=pi3orama@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).