From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29563 invoked by alias); 18 Nov 2007 01:24:56 -0000 Received: (qmail 29555 invoked by uid 22791); 18 Nov 2007 01:24:56 -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:24:53 +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 123473DA100; Sun, 18 Nov 2007 14:24:45 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 6BD008FC6D; Sun, 18 Nov 2007 14:24:42 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18239.37977.82092.169421@kahikatea.snap.net.nz> Date: Sun, 18 Nov 2007 01:24:00 -0000 To: Eli Zaretskii Cc: gdb-patches@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-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-11/txt/msg00355.txt.bz2 > Thanks for your suggestions, I fixed the manual as shown below: > > 2007-11-17 Eli Zaretskii > > * gdb.texinfo (Set Breaks, Disabling): Clarify behavior of > breakpoints with multiple locations. > (Breakpoint Menus): Improve wording. Since the concept of a parent breakpoint has been used, perhaps this could be used with "header row". Also breakpoint-number is abbreviated to BNUM elsewhere. Here are a few ideas: -- Nick http://www.inet.net.nz/~nickrob *** gdb.texinfo.~1.446.~ 2007-11-18 13:23:21.000000000 +1300 --- gdb.texinfo 2007-11-18 14:19:45.000000000 +1300 *************** In all those cases, @value{GDBN} will in *** 3061,3072 **** the relevant locations. A breakpoint with multiple locations is displayed in the breakpoint ! table using several rows---one header row, followed by one row for ! each breakpoint location. The header row has @samp{} in the ! address column. The rows for individual locations contain the actual ! addresses for locations, and show the functions to which those ! locations belong. The number column for a location is of the form ! @var{breakpoint-number}.@var{location-number}. For example: --- 3061,3074 ---- the relevant locations. A breakpoint with multiple locations is displayed in the breakpoint ! table using several rows---one header row for the parent breakpoint, ! followed by one row for each breakpoint location. The header row has ! @samp{} in the address column. The rows for individual ! locations contain the actual addresses for locations, and show the ! functions to which those locations belong. The number column for a ! location is of the form @var{bnum}.@var{lnum} where @var{bnum} is is ! the number of the parent breakpoint and @var{lnum} the location ! number. For example: *************** Num Type Disp Enb Address *** 3080,3093 **** @end smallexample Each location can be individually enabled or disabled by passing ! @var{breakpoint-number}.@var{location-number} as argument to the ! @code{enable} and @code{disable} commands. Note that you cannot ! delete the individual locations from the list, you can only delete the ! entire list of locations that belong to their parent breakpoint (with ! the @kbd{delete @var{num}} command, where @var{num} is the number of ! the parent breakpoint, 1 in the above example). Disabling or enabling ! the parent breakpoint (@pxref{Disabling}) affects all of the locations ! that belong to that breakpoint. @cindex pending breakpoints It's quite common to have a breakpoint inside a shared library. --- 3082,3094 ---- @end smallexample Each location can be individually enabled or disabled by passing ! @var{bnum}.@var{lnum} as argument to the @code{enable} and ! @code{disable} commands. Note that you cannot delete the individual ! locations from the list, you can only delete the entire list of ! locations that belong to their parent breakpoint (with the @kbd{delete ! @var{bnum}} command, where @var{bnum} is 1 in the above example). ! Disabling or enabling the parent breakpoint (@pxref{Disabling}) ! affects all of the locations that belong to that breakpoint. @cindex pending breakpoints It's quite common to have a breakpoint inside a shared library.