From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15023 invoked by alias); 27 Jan 2009 05:09:40 -0000 Received: (qmail 15014 invoked by uid 22791); 27 Jan 2009 05:09:38 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Jan 2009 05:09:33 +0000 Received: from mailhost2.vmware.com (mailhost2.vmware.com [10.16.67.167]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 421E949008; Mon, 26 Jan 2009 21:09:32 -0800 (PST) Received: from [10.20.92.151] (promb-2s-dhcp151.eng.vmware.com [10.20.92.151]) by mailhost2.vmware.com (Postfix) with ESMTP id 281BC8E5C5; Mon, 26 Jan 2009 21:09:32 -0800 (PST) Message-ID: <497E9432.4010007@vmware.com> Date: Tue, 27 Jan 2009 05:09:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: Jakob Engblom CC: 'Marc Khouzam' , 'Joel Brobecker' , 'teawater' , 'David Daney' , "gdb@sourceware.org" Subject: Re: Discussing the next GDB release (GDB 7.0?) References: <20090116033948.GI31296@adacore.com> <6D19CA8D71C89C43A057926FE0D4ADAA06C52409@ecamlmw720.eamcs.ericsson.se> <001a01c97b2c$75824960$6086dc20$@com> In-Reply-To: <001a01c97b2c$75824960$6086dc20$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: 2009-01/txt/msg00179.txt.bz2 Jakob Engblom wrote: >> For what its worth, I can't speak to the level of criticality of >> process record and replay, but we would really like to see this in >> the 7.0 release. >> >> I am almost ready with the Eclipse support for it (I manually >> applied the patches to GDB) and plan on doing a demo at EclipseCon. >> From what I was told, reverse debugging generates a lot of interest >> in people and would be a great addition to GDB. >> >> Great work on the whole Reverse Debugging feature and >> Process Record and Replay! > > I wonder if record/replay and reverse debugging are one and the same feature > from the perspective of inclusion in gdb 7.0? It seems so from the above? > Logically, they can be separated into at least five parts: > > * revexec support in gdb-serial > > * reveexec support in MI > > * revexec support in the gdb kernel > > * record/replay as one way to effect revexec for the case of > x86-linux-user-process > > * revexec from external sources, such as VMWare, Simics, and other simulators > > Which parts of these are currently under consideration for inclusion in the > first 7.0 release? The first three are already in (except I'm a little fuzzy about the state of MI). Oh, and by the way (Eli and Joel), I owe you a NEWS entry. The fourth (process record/replay) is what's currently on the table for discussion. The fifth bullet item (reverse exec from external sources such as VMware, Virtutech etc). doesn't require any approval or action on the part of the gdb maintainers, unless it uncovers a bug or problem in the gdb parts. Y'all (including me) can just go to town! ;-)