From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26555 invoked by alias); 12 Feb 2010 15:33:39 -0000 Received: (qmail 26544 invoked by uid 22791); 12 Feb 2010 15:33:38 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS,WEIRD_PORT 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; Fri, 12 Feb 2010 15:33:34 +0000 Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id o1CFZ6tv005797; Fri, 12 Feb 2010 09:35:06 -0600 Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.197]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Fri, 12 Feb 2010 10:33:31 -0500 From: Marc Khouzam To: "'Vladimir Prus'" , "'gdb@sources.redhat.com'" Date: Fri, 12 Feb 2010 15:33:00 -0000 Subject: RE: [MI] -exec-return or CLI 'return' do not trigger MI events Message-ID: References: In-Reply-To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: 2010-02/txt/msg00097.txt.bz2 > -----Original Message----- > From: gdb-owner@sourceware.org=20 > [mailto:gdb-owner@sourceware.org] On Behalf Of Vladimir Prus > Sent: Friday, February 12, 2010 5:28 AM > To: gdb@sources.redhat.com > Subject: Re: [MI] -exec-return or CLI 'return' do not trigger=20 > MI events >=20 > Marc Khouzam wrote: >=20 > > Hi, > >=20 > > I just noticed that GDB 7.0.1 does not issue MI events > > *running and *stopped for the CLI 'return' command. > > This is the relevant output, while the whole (small) > > session is after. > >=20 > > (gdb) -exec-return > >=20 > ^done,frame=3D{level=3D"0",addr=3D"0x08048412",func=3D"foo",args=3D[],fi > le=3D"a.cc",fullname=3D"/local/lmckhou/testing/a.cc",line=3D"6"} > > (gdb) return > > &"return\n" > > ~"#0 main () at a.cc:9\n" > > ~"9\t return 0;\n" > > ^done > >=20 > > Do you want me to write a bug? >=20 > For all I can tell, the 'return' command does not actually=20 > resume the target. > It just pops the stack. Ok, but how does the frontend know the stack has been poped and the editor should show a new line? When we use GDB 7.0 we only listen for MI events to update the frontend data. I'll have to fix this for '-exec-return' anyway to support GDB 7.0, but with respect to GDB itself, aren't we missing some MI event then? Thanks Marc