From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8156 invoked by alias); 16 Dec 2008 14:45:14 -0000 Received: (qmail 8139 invoked by uid 22791); 16 Dec 2008 14:45:13 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from imr1.ericy.com (HELO imr1.ericy.com) (198.24.6.9) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Dec 2008 14:44:30 +0000 Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id mBGEmEBk028452; Tue, 16 Dec 2008 08:48:14 -0600 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 Dec 2008 08:44:27 -0600 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: reverse for GDB/MI Date: Tue, 16 Dec 2008 14:45:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA06A6EF6D@ecamlmw720.eamcs.ericsson.se> In-Reply-To: <026f01c95f5a$657b8920$30729b60$@com> References: <49463870.6080302@virtutech.com> <6D19CA8D71C89C43A057926FE0D4ADAA06A3DD92@ecamlmw720.eamcs.ericsson.se> <026f01c95f5a$657b8920$30729b60$@com> From: "Marc Khouzam" To: "Jakob Engblom" , "Tomas Holmberg" , , "Michael Snyder" 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: 2008-12/txt/msg00309.txt.bz2 =20 > From: Jakob Engblom [mailto:jakob@virtutech.com]=20 > Sent: Tuesday, December 16, 2008 3:44 AM >=20 > > One little annoying point is the command > > -gdb-set exec-direction [forward | reverse] > > When this command is issued, to be really correct, MI would need an > > event to notify a frontend that the exec-direction has changed. > > This is in case the exec-direction is changed in the console or from > > another window. >=20 > This is to retain compatibility with the normal gdb=20 > command-line commands for > reversing. According to an earlier discussion in October,=20 > this command was part > of the Michael Snyder patches to support rev exec, and it was=20 > decided then not > to change the commands.=20 >=20=20 > > Another option, to avoid adding a new event, is if we could=20 > disable the > > changing of exec-direction when running in MI, and simulate=20 > it in the > > frontend. > > The frontend could simply keep track of the exec-direction=20 > chosen by the > > user > > and issue reverse commands or forward commands, appropriately. >=20 > The simplest solution is to have no "direction" at all, but=20 > just a set of > reverse-X and forward-X commands. But that is not inline=20 > with the main gdb user > interface as it stands currently as we understand it.=20 I think it is nice from a user's perspective to have the two approaches to reverse debugging. So, I actually like the exec-direction command from a CLI perspective. It was for MI, that I felt it caused complications. But now that I think about it, DSF-GDB provides a console to the user, which can accept CLI commands. Therefore, I can imagine that if the user has set the exec-direction to reverse (even through the Eclipse UI), he would expect 'next' and 'step'=20 to work backwards if typed in the console. Sigh... So, I think that the best solution for MI is to have an event to indicate a change of exec-direction. Disabling that toggle like I originally suggested could still work but would require the frontend to simulated it by also converting 'next' into 'reverse-next' when typed in the command line, which is getting ugly... Marc