From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18659 invoked by alias); 20 Apr 2008 09:09:24 -0000 Received: (qmail 18650 invoked by uid 22791); 20 Apr 2008 09:09:22 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout5.012.net.il (HELO mtaout5.012.net.il) (84.95.2.13) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 20 Apr 2008 09:09:03 +0000 Received: from HOME-C4E4A596F7 ([80.230.59.104]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0JZM00D6LA2CJJ21@i_mtaout5.012.net.il> for gdb@sourceware.org; Sun, 20 Apr 2008 12:23:01 +0300 (IDT) Date: Sun, 20 Apr 2008 14:32:00 -0000 From: Eli Zaretskii Subject: Re: breaking on open(2) on linux In-reply-to: <200804161209.31313.vladimir@codesourcery.com> X-012-Sender: halo1@inter.net.il To: Vladimir Prus Cc: nickrob@snap.net.nz, leisner@rochester.rr.com, gdb@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <200804122237.m3CMbtfl022914@dell2.home> <200804151211.33371.vladimir@codesourcery.com> <200804161209.31313.vladimir@codesourcery.com> 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: 2008-04/txt/msg00179.txt.bz2 > From: Vladimir Prus > Date: Wed, 16 Apr 2008 12:09:30 +0400 > Cc: nickrob@snap.net.nz, leisner@rochester.rr.com, gdb@sourceware.org > > On Wednesday 16 April 2008 00:34:30 Eli Zaretskii wrote: > > > From: Vladimir Prus > > > Date: Tue, 15 Apr 2008 12:11:33 +0400 > > > > > > The multiple location support only works if there line number information > > > for all locations. > > > > This is important enough to mention in the manual. Is it there? if it > > is, I cannot find it. > > It's not there. It is now (committed): 2008-04-20 Eli Zaretskii * gdb.texinfo (Set Breaks): Mention that multiple location breakpoints need line number info. Add index entries. Index: gdb/doc/gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.482 diff -u -r1.482 gdb.texinfo --- gdb/doc/gdb.texinfo 20 Apr 2008 00:03:25 -0000 1.482 +++ gdb/doc/gdb.texinfo 20 Apr 2008 09:04:38 -0000 @@ -3072,11 +3072,12 @@ the breakpoints are conditional, this is even useful (@pxref{Conditions, ,Break Conditions}). +@cindex multiple locations, breakpoints +@cindex breakpoints, multiple locations It is possible that a breakpoint corresponds to several locations in your program. Examples of this situation are: @itemize @bullet - @item For a C@t{++} constructor, the @value{NGCC} compiler generates several instances of the function body, used in different cases. @@ -3088,11 +3089,14 @@ @item For an inlined function, a given source line can correspond to several places where that function is inlined. - @end itemize In all those cases, @value{GDBN} will insert a breakpoint at all -the relevant locations. +the relevant locations@footnote{ +As of this writing, multiple-location breakpoints work only if there's +line number information for all the locations. This means that they +will generally not work in system libraries, unless you have debug +info with line numbers for them.}. A breakpoint with multiple locations is displayed in the breakpoint table using several rows---one header row, followed by one row for