From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20804-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 8014 invoked by alias); 4 Mar 2005 07:24:00 -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 7822 invoked from network); 4 Mar 2005 07:23:46 -0000
Received: from unknown (HELO viper.snap.net.nz) (202.37.101.8)
  by sourceware.org with SMTP; 4 Mar 2005 07:23:46 -0000
Received: from farnswood.snap.net.nz (p128-tnt1.snap.net.nz [202.124.110.128])
	by viper.snap.net.nz (Postfix) with ESMTP id 612EA4702CA;
	Fri,  4 Mar 2005 20:23:44 +1300 (NZDT)
Received: by farnswood.snap.net.nz (Postfix, from userid 501)
	id 5CE4B62FBE; Fri,  4 Mar 2005 07:22:15 +0000 (GMT)
From: Nick Roberts <nickrob@snap.net.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16936.3238.730574.794373@farnswood.snap.net.nz>
Date: Fri, 04 Mar 2005 07:24:00 -0000
To: Andrew Cagney <cagney@gnu.org>
Cc: Bob Rossi <bob@brasko.net>, gdb@sources.redhat.com
Subject: Re: fullname descriptor with -break-list
In-Reply-To: <420787A3.2070605@gnu.org>
References: <16902.30786.705993.121669@farnswood.snap.net.nz>
	<20050206210637.GB19609@white>
	<16902.45534.858929.941689@farnswood.snap.net.nz>
	<20050207134829.GA21985@white>
	<420787A3.2070605@gnu.org>
X-SW-Source: 2005-03/txt/msg00031.txt.bz2

 > >>-exec-run
 > >>^running
 > >>(gdb) 
 > >>*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x080486e2",func="myprint",args=[{name="i",value="0"},{name="j",value="0"}],file="myprint.c",line="5"}
 ...
 > The way that message is generated is a massive kludge - so the 
 > underlying code could do with a cleanup - separate the code determining 
 > why the process stopped from the code printing the stop reason.

Just a short note for the future:

As *stopped is asynchronous output and not that of a specific MI command, I
also think this output should appear even if a CLI command has been invoked.

Currently a GDB session might look like:

&"b main\n"
~"Breakpoint 1 at 0x80484cf: file myprog.c, line 48.\n"
^done
(gdb) 
run
&"run\n"
~"Starting program: /home/nick/myprog \n"
~"\n"
~"Breakpoint 1, main (argc=1, argv=0xbffff794) at myprog.c:48\n"
~"48\t  int i, n, m[10]={0,1,4,9,16,25,36,49,64,81};\n"
^done
(gdb) 

but I think it should look something like:


&"b main\n"
~"Breakpoint 1 at 0x80484cf: file myprog.c, line 48.\n"
^done
(gdb) 
run
&"run\n"
~"Starting program: /home/nick/myprog \n"
~"\n"
~"Breakpoint 1, main (argc=1, argv=0xbffff794) at myprog.c:48\n"
~"48\t  int i, n, m[10]={0,1,4,9,16,25,36,49,64,81};\n"
^done
(gdb) 
*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x080484cf",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbffff794"}],file="myprog.c",line="48"}
(gdb) 


or with "-interpreter-exec console run" if direct CLI is going to be removed.

>From Emacs point of view, this would mean the CLI commands could be entered in
the GUD buffer.


Nick