From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9468 invoked by alias); 21 May 2008 05:05:20 -0000 Received: (qmail 9460 invoked by uid 22791); 21 May 2008 05:05:19 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 May 2008 05:04:59 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JygVI-0004n7-4P for gdb@sources.redhat.com; Wed, 21 May 2008 05:04:44 +0000 Received: from 78.158.192.230 ([78.158.192.230]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 May 2008 05:04:44 +0000 Received: from vladimir by 78.158.192.230 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 May 2008 05:04:44 +0000 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: [GDB/MI] missing token in "stopped" output after -exec-run? Date: Wed, 21 May 2008 05:05:00 -0000 Message-ID: References: <20080521035924.GA4148@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.5 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: 2008-05/txt/msg00150.txt.bz2 Joel Brobecker wrote: .... > *stopped,reason="breakpoint-hit",disp="del",bkptno="1",thread-id="1",frame={addr="0x08048332",func="main",args=[],file="foo.c",fullname="/home/no-backup/brobecke/head-merge/ex/foo.c",line="6"} > > A few weeks ago, the output looked like this: > > 232-exec-run > 232^running > (gdb) > 232*stopped,reason="breakpoint-hit",disp="del",... > > The token was preserved. Is the new behavior intended? Yes (and I've explicitly posted to the list about this change, quite some time before actually changing things). The situation is: 1. In current gdb, the token actually provides no information (since only on run command can be active at a time). 2. No frontend author stepped in to say they care. 3. In non-stop mode, keeping the token is almost impossible. 4. The implementation of printing of the token was a mess. Does it cause any problems for you? - Volodya