From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16081 invoked by alias); 10 Feb 2009 20:50:17 -0000 Received: (qmail 16072 invoked by uid 22791); 10 Feb 2009 20:50:16 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_20,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; Tue, 10 Feb 2009 20:50:08 +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 n1AKnv6C010512; Tue, 10 Feb 2009 14:49:58 -0600 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Feb 2009 14:44:35 -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: [RFA] fix *stopped for CLI commands Date: Tue, 10 Feb 2009 20:50:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA06E84D64@ecamlmw720.eamcs.ericsson.se> In-Reply-To: <200902061045.18508.vladimir@codesourcery.com> References: <200902061045.18508.vladimir@codesourcery.com> From: "Marc Khouzam" To: "Vladimir Prus" , , "Nick Roberts" 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-02/txt/msg00226.txt.bz2 > Vladimir Prus > Sent: Friday, February 06, 2009 2:45 AM > To: gdb-patches@sources.redhat.com; Nick Roberts; Marc Khouzam > Subject: [RFA] fix *stopped for CLI commands >=20 > This patch fixes this by making MI observer print frame=20 > again, into MI uiout, > if necessary. I've applied the patch and tried it out. It works as expected but it 'allowed' me to run into another problem. When issuing a CLI command that triggers a ^running event, the token id is not part of the ^running event anymore. You can see this in the summarized session below. 26-exec-run [...] 26^running <-- token is there for MI command *running,thread-id=3D"all" (gdb)=20 [...] (gdb)=20 27run &"run\n" [...] ^running <-- token is not there for CLI command *running,thread-id=3D"all" (gdb)=20 I never noticed this before because DSF-GDB never uses CLI commands that would trigger a ^running. So, to DSF-GDB it looks like the=20 CLI command never completed. Thanks Marc