This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: breaking on open(2) on linux


> From: Vladimir Prus <vladimir@codesourcery.com>
> 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 <vladimir@codesourcery.com>
> > > 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  <eliz@gnu.org>

	* 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]