From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22052 invoked by alias); 4 Apr 2003 22:19:55 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 22044 invoked from network); 4 Apr 2003 22:19:54 -0000 Received: from unknown (HELO mail-out1.apple.com) (17.254.0.52) by sources.redhat.com with SMTP; 4 Apr 2003 22:19:54 -0000 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out1.apple.com (8.12.9/8.12.9) with ESMTP id h34MJr3h007266 for ; Fri, 4 Apr 2003 14:19:53 -0800 (PST) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Fri, 4 Apr 2003 14:19:45 -0800 Received: from apple.com (inghji.apple.com [17.201.22.240]) by scv1.apple.com (8.12.9/8.12.9) with ESMTP id h34MJrvu003454 for ; Fri, 4 Apr 2003 14:19:53 -0800 (PST) Date: Fri, 04 Apr 2003 22:19:00 -0000 Subject: Re: Add fullname to breakpoint output Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Jim Ingham To: gdb@sources.redhat.com Content-Transfer-Encoding: 7bit In-Reply-To: <1049485092.22026.ezmlm@sources.redhat.com> Message-Id: <8E93EF0A-66EB-11D7-A344-00039379E320@apple.com> X-SW-Source: 2003-04/txt/msg00051.txt.bz2 > Hi, > > I wrote a patch that adds the fullname to breakpoint output. > > (gdb) > -break-insert main > ^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y", > addr="0x080483c3",func="main",fullname="/home/bob/cvs/src/gdb/test.c", > file="test.c",line="8",times="0"} > (gdb) > > I would like confirmation on this before I go through the effort to > fix the testsuite. There is 85 test cases to fix. I would like to know > that there is a general consensus that this patch would be an > acceptable > idea before I fix the testsuite. > > Thanks, > Bob Rossi > > Does it do this for both the CLI and the MI, or just the MI? We found working on Project Builder that it was often more convenient to add extra info to the MI output, but not to the CLI. In my view, the CLI should aim at minimalism, since a human being is scanning it and too much information would be confusing. The MI is intended to be scanned by a program, so we should feel free to cram in whatever might be useful - within reason of course... For this reason, when we found PB needed an extra bit of data which might not be so useful to the CLI user, we would just add it to the MI only. This is a little unsatisfying in implementation, since it means you have if (ui_out_is_mi_like (uiout)) { } scattered through non-interpreter specific code. But this is better than cluttering up the CLI output for stuff that is more interesting to a front-end... Jim -- Jim Ingham jingham@apple.com Developer Tools Apple Computer