From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20855-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 10831 invoked by alias); 9 Mar 2005 02:40:07 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 10731 invoked from network); 9 Mar 2005 02:39:59 -0000
Received: from unknown (HELO lakermmtao06.cox.net) (68.230.240.33)
  by sourceware.org with SMTP; 9 Mar 2005 02:39:59 -0000
Received: from white ([68.9.64.121]) by lakermmtao06.cox.net
          (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP
          id <20050309023953.YNTY21504.lakermmtao06.cox.net@white>
          for <gdb@sources.redhat.com>; Tue, 8 Mar 2005 21:39:53 -0500
Received: from bob by white with local (Exim 3.35 #1 (Debian))
	id 1D8r77-0002t8-00
	for <gdb@sources.redhat.com>; Tue, 08 Mar 2005 21:39:57 -0500
Date: Wed, 09 Mar 2005 02:40:00 -0000
From: Bob Rossi <bob@brasko.net>
To: GDB <gdb@sources.redhat.com>
Subject: MI output command error
Message-ID: <20050309023957.GB10866@white>
Mail-Followup-To: GDB <gdb@sources.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-SW-Source: 2005-03/txt/msg00082.txt.bz2

Hi,

The doco for -break-watch has,
   (gdb)
   -break-watch x
   ^done,wpt={number="2",exp="x"}
   (gdb)
   -exec-continue
   ^running
   ^done,reason="watchpoint-trigger",wpt={number="2",exp="x"},
   value={old="-268439212",new="55"},
   frame={func="main",args=[],file="recursive2.c",line="5"}
   (gdb)

However, when I run it with GDB from CVS, I get,

   (gdb) 
   -break-watch argc
   ^done,wpt={number="2",exp="argc"}
   (gdb) 
   -exec-continue
   ^running
   (gdb) 
   *stopped,reason="watchpoint-scope",wpnum="2",thread-id="0",frame={addr="0x40039dc9",func="__libc_start_main",args=[],from="/lib/libc.so.6"}
   (gdb) 

The problem is, the -exec-continue command in CVS has an extra '(gdb)'
in it after '^running'. I don't know if the doco or GDB is correct.
I do know that I think GDB is conforming to the MI output command
syntax, even though I think the documentation output looks more correct.

Was the extra "(gdb)" added to make the output command match the syntax?
Is this a bug in the doco or in GDB?

Thanks,
Bob Rossi