From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29459 invoked by alias); 9 Jun 2011 13:05:44 -0000 Received: (qmail 29448 invoked by uid 22791); 9 Jun 2011 13:05:43 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST X-Spam-Check-By: sourceware.org Received: from mail-pv0-f169.google.com (HELO mail-pv0-f169.google.com) (74.125.83.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 09 Jun 2011 13:05:29 +0000 Received: by pvc12 with SMTP id 12so883108pvc.0 for ; Thu, 09 Jun 2011 06:05:29 -0700 (PDT) Received: by 10.143.153.7 with SMTP id f7mr93064wfo.379.1307624729143; Thu, 09 Jun 2011 06:05:29 -0700 (PDT) Received: from [10.5.0.40] ([159.226.43.45]) by mx.google.com with ESMTPS id t15sm1707760wfh.4.2011.06.09.06.05.26 (version=SSLv3 cipher=OTHER); Thu, 09 Jun 2011 06:05:28 -0700 (PDT) Message-ID: <4DF0C4C2.3000600@gmail.com> Date: Thu, 09 Jun 2011 13:05:00 -0000 From: pi3orama User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110518 Lightning/1.0b3pre Thunderbird/3.1.10 MIME-Version: 1.0 To: paawan oza CC: Pedro Alves , gdb@sourceware.org Subject: Re: ReBranch - a record-replay debugging tool References: <1307602807.17016.ezmlm@sourceware.org> <4DF0748B.2060703@gmail.com> <201106091027.20575.pedro@codesourcery.com> <641906.35134.qm@web112513.mail.gq1.yahoo.com> In-Reply-To: <641906.35134.qm@web112513.mail.gq1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-06/txt/msg00050.txt.bz2 I've changed the description in the site. Only replay phase use gdbserver, recording phase is standalone. In fact, there is a GUI tool (rebranchk.tcl) which allow users to replay without GDB. > Hi, > > in the site it says: > > > GDB > The replay is driven by GDB, nearly all GDB commands are useable. > > Do I understand that recording is adopted differently ? > > Regards,Oza. > > > > ________________________________ > From: Pedro Alves > To: gdb@sourceware.org > Cc: pi3orama > Sent: Thu, June 9, 2011 2:57:20 PM > Subject: Re: ReBranch - a record-replay debugging tool > > 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. >