From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32214 invoked by alias); 18 Nov 2007 01:32:51 -0000 Received: (qmail 32200 invoked by uid 22791); 18 Nov 2007 01:32:50 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 18 Nov 2007 01:32:49 +0000 Received: from kahikatea.snap.net.nz (245.31.255.123.static.snap.net.nz [123.255.31.245]) by viper.snap.net.nz (Postfix) with ESMTP id 641333DA005; Sun, 18 Nov 2007 14:32:46 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id C38E18FC6D; Sun, 18 Nov 2007 14:32:43 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18239.38458.695867.472660@kahikatea.snap.net.nz> Date: Sun, 18 Nov 2007 01:32:00 -0000 To: Eli Zaretskii Cc: Vladimir Prus , gdb@sources.redhat.com Subject: Re: Multiple breakpoint locations In-Reply-To: References: <18233.63439.953202.586908@kahikatea.snap.net.nz> X-Mailer: VM 7.19 under Emacs 23.0.50.49 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-11/txt/msg00171.txt.bz2 > > The manual lists cases where a given function in source can correspond to > > several PC values, and they say: > > > > In all those cases, @value{GDBN} will insert a breakpoint at all > > the relevant locations. > > > > So it happens automatically. > > Well, I think it's not explicit enough. I will try to add some more > explicit explanations when I have time. The only way I've managed to create breakpoints at multiple locations is by specifying a line number inside the template/constructor. For templates I understand that the breakpoints are for different types, e.g., float, int as used by the program. For constructors: * For a C++ constructor, the GCC compiler generates several instances of the function body, used in different cases. I don't understand what the second breakpoint refers to, or why there may be more than one instance. So I think, at some point, a separate node, or one grouped with breakpoint menus to highlight the differences, would be a good idea. Other things, like needing to include the return type in the template name when specifying a breakpoint location could also be included. -- Nick http://www.inet.net.nz/~nickrob