From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10097 invoked by alias); 25 Jan 2006 13:45:24 -0000 Received: (qmail 10040 invoked by uid 22791); 25 Jan 2006 13:45:23 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao03.cox.net (HELO eastrmmtao03.cox.net) (68.230.240.36) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 25 Jan 2006 13:45:19 +0000 Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao03.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060125134520.ZESY29285.eastrmmtao03.cox.net@localhost.localdomain>; Wed, 25 Jan 2006 08:45:20 -0500 Received: from bob by localhost.localdomain with local (Exim 4.52) id 1F1ky5-0005SA-I3; Wed, 25 Jan 2006 08:45:49 -0500 Date: Wed, 25 Jan 2006 13:45:00 -0000 From: Bob Rossi To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] Add fullname field for MI -break-info command Message-ID: <20060125134549.GB20856@brasko.net> Mail-Followup-To: Vladimir Prus , gdb-patches@sources.redhat.com References: <200601241932.16022.ghost@cs.msu.su> <20060125121030.GJ28357@brasko.net> <200601251544.27477.ghost@cs.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601251544.27477.ghost@cs.msu.su> User-Agent: Mutt/1.5.9i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00407.txt.bz2 > > > > Also, don't forget about the documentation. > > > > > > Well, at the moment the -break-info command is not documented at all, so > > > there's no place where I can add the extra "fullname" field. > > > > Hmm, there is a section in the gdb.texinfo manual that says > > @c REDUNDANT??? > > Get information about a single breakpoint. > > how is this command useful, instead of just using -break-list? > > Hmm, so I should update all examples of "-break-list" output as well? What > path should I put there? Is /home/foo/bar/.c > fine? Yes, please update the documentation for -break-list, and I don't know if you should even bother with -break-info. I still don't know if that command should exist if it's identical to -break-list. A machine interface does not need 2 commands for the same functionatlity, IMO. For -file-list-exec-source-files I used this path as an example, @smallexample (@value{GDBP}) 123-file-list-exec-source-file 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c" (@value{GDBP}) @end smallexample so, yes, something like you have is OK. Bob Rossi