From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20648 invoked by alias); 13 Jan 2006 15:23:57 -0000 Received: (qmail 20640 invoked by uid 22791); 13 Jan 2006 15:23:56 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 13 Jan 2006 15:23:54 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1ExQmN-0002ZQ-PX; Fri, 13 Jan 2006 10:23:51 -0500 Date: Fri, 13 Jan 2006 15:23:00 -0000 From: Daniel Jacobowitz To: Paul Hilfinger Cc: gdb@sourceware.org Subject: Re: [RFC] multiple breakpoints from FILE:LINE Message-ID: <20060113152350.GA9758@nevyn.them.org> Mail-Followup-To: Paul Hilfinger , gdb@sourceware.org References: <20060113104212.0B28848CBD8@nile.gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060113104212.0B28848CBD8@nile.gnat.com> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00108.txt.bz2 I'll read the rest of the replies momentarily but... On Fri, Jan 13, 2006 at 05:42:12AM -0500, Paul Hilfinger wrote: > > In response to > > break FUNCTION > > in C++, GDB currently presents one with a list of choices when FUNCTION > is overloaded. However, this is not the only case in which the target > of a 'break' command is ambiguous. Consider > > break FILENAME:LINENUM > > Normally, this refers to a single location in a program, but if this line > is in the middle of a C++ template, a multiply #included file, or an > Ada generic definition, it may refer to several locations. Currently, > GDB chooses one of these silently. We have discussed this issue many times in the past, as recently as two weeks ago. In the beginning of 2005 I posted a prototype patch to set only a single breakpoint, but associate it with multiple locations. I still firmly believe that that is the correct solution. However, the patch was never finished. Those menus have got to go. They're (a) confusing to users (in my opinion, no real data), and (b) extremely awkward for graphical frontends. -- Daniel Jacobowitz CodeSourcery