From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7613 invoked by alias); 30 Apr 2009 14:43:47 -0000 Received: (qmail 7602 invoked by uid 22791); 30 Apr 2009 14:43:46 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from imr2.ericy.com (HELO imr2.ericy.com) (198.24.6.3) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Apr 2009 14:43:41 +0000 Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n3UEhT9b032366; Thu, 30 Apr 2009 09:43:29 -0500 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Apr 2009 09:42:32 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Process record and replay checked in to main trunk Date: Thu, 30 Apr 2009 14:43:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA075CA8EE@ecamlmw720.eamcs.ericsson.se> In-Reply-To: References: From: "Marc Khouzam" To: "Hui Zhu" , Cc: "Pedro Alves" , "Michael Snyder" , "Thiago Jung Bauermann" , "Eli Zaretskii" , "Mark Kettenis" X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00810.txt.bz2 =20 > Process record and replay make gdb can record inferior execute log and > replay (include reverse debug). > Now, it support I386-Linux single-thread single-inferior native debug. >=20 > It was checked in today. Congratulations! I've checked-out the new HEAD and running PRecord in Eclipse with no patches. > Guys, please work on it if you interesting with some of them. And > feel free tell me your ideas and comments. It will help precord a > lot. Here are some things I think would be nice: 1- The handling of queries in PRecord as we discussed in http://sourceware.org/ml/gdb/2009-03/msg00194.html 2- speed (but you already mentioned you will work on this) 3- Some MI support - 'record' and 'stoprecord' could have an MI equivalent - trying to get the MI commands for Reverse debugging done - *stopped MI event could/should have a special 'reason' field when it is triggered because Replay execution is finished. Currently, there is no 'reason' field in this case. Having the 'reason' field would allow a fronten to optionally resume the execution at that point, instead of mysteriously stopping when the Replay execution is finished. I'm sure more suggestion will arise as people start using it. Again, good work! Marc