This is the mail archive of the
mailing list for the GDB project.
Re: ReBranch - a record-replay debugging tool
- From: pi3orama <pi3orama at gmail dot com>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb at sourceware dot org
- Date: Thu, 09 Jun 2011 20:52:57 +0800
- Subject: Re: ReBranch - a record-replay debugging tool
- References: <firstname.lastname@example.org> <email@example.com>
I have add GDB's copyright notice back, you can check for it in the git
A comparison of GDB record/replay and ReBranch has been added to the
google code site.
A pdf describe the mechanism of ReBranch has been uploaded to the site
and google doc:
Thank you for your kindly advise.
> On Thursday 09 June 2011 12:57:18, firstname.lastname@example.org wrote:
>> Thank you for your advise. I have changed license, added a COPYING file in
>> the code, and added copyright header into every source files.
> Thanks a bunch!
> One detail. Files that had been derived from other GPL files
> should not lose the original copyright notice. Of course
> you can _add_ a note on your own copyright. That is, e.g.,
> on exception.h|c, I suggest something like:
> /* Copyright (C) 1986, 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
> 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
> 2009, 2010, 2011 Free Software Foundation, Inc.
> Copyright (C) 2009, 2010, 2011 Nan Wang
> This file is part of ReBranch. Originally based on exceptions.c from GDB.
> (there may be other files, I really haven't checked)
> Still very much looking forward for a high level outline of ReBranch's
> record/replay strategy, and how it differs from GDB's target record. :-)