From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7551 invoked by alias); 12 Jul 2009 18:50:56 -0000 Received: (qmail 7542 invoked by uid 22791); 12 Jul 2009 18:50:55 -0000 X-SWARE-Spam-Status: No, hits=-2.3 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; Sun, 12 Jul 2009 18:50:49 +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 n6CIntd7027314; Sun, 12 Jul 2009 13:50:03 -0500 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sun, 12 Jul 2009 13:50:00 -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: Testing of reverse debug commands Date: Sun, 12 Jul 2009 18:50:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA07B71A36@ecamlmw720.eamcs.ericsson.se> In-Reply-To: <4A5A19FC.9050206@vmware.com> References: <4A5930EE.3040201@vmware.com> <20090712080145.GB10756@adacore.com> <20090712142834.GA3355@host0.dyn.jankratochvil.net> <4A5A19FC.9050206@vmware.com> From: "Marc Khouzam" To: "Michael Snyder" , "Jan Kratochvil" Cc: "Joel Brobecker" , , "Hui Zhu" 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-07/txt/msg00083.txt.bz2 > -----Original Message----- > From: gdb-owner@sourceware.org=20 > [mailto:gdb-owner@sourceware.org] On Behalf Of Michael Snyder > Sent: July-12-09 1:15 PM > To: Jan Kratochvil > Cc: Joel Brobecker; gdb@sourceware.org; Hui Zhu > Subject: Re: Testing of reverse debug commands >=20 > Jan Kratochvil wrote: > > On Sun, 12 Jul 2009 10:01:45 +0200, Joel Brobecker wrote: > >>> gdb_test "record" "" "Turn on process record" > >>> # FIXME: command ought to acknowledge, so we can test=20 > if it succeeded. > >> This is just a shot in the dark since I really don't have much time > >> to double-check this, but does gdb_test_multiple allow you=20 > to verify > >> that no output was generated? For some reason, I thought it did. > >=20 > > This one works but not sure if it cannot have some problems: > >=20 > > set cmd "set verbose 0" > > gdb_test $cmd "[string_to_regexp $cmd]" >=20 > Hmm, ok, three people so far have responded with > work-arounds (thanks). >=20 > Does that mean y'all lean toward NOT making the > commands generate some output of their own? >=20 > Now would be the time to decide, before the first official release... =46rom a frontend perspective, the current 'record' command is not very good. First, there is no MI equivalent, although that is not a big deal. But since it does not report error, the frontend must always assumes that the command worked. Below you can see that using 'record stop' directly will give a ^done instead of an ^error when it fails (although there is an error message but we don't parse those in Eclipse). Also, using -interpreter-exec is even worse as even the error message is gone. (gdb)=20 record stop &"record stop\n" ~"Process record is not started.\n" ^done (gdb)=20 -interpreter-exec console record stop ^done (gdb)=20 So, I think some improvement would be nice for frontends. There is also a need to handle the default answers of queries better for a frontend. They are almost entirely used by PRecord. I've been meaning to write a patch about that. I'll try to=20 get to it soon unless someone else gets to it first :-) Marc