From 7ab317d5f4d9ef1d4ed52693f916f191fd2de1b1 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Mon, 14 Nov 2011 13:18:19 -0700 Subject: [PATCH 4/4] doc changes --- gdb/ChangeLog | 4 ++++ gdb/NEWS | 6 ++++++ gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdb.texinfo | 9 ++++----- 4 files changed, 18 insertions(+), 5 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 7abd7ef..b4b3f4b 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,9 @@ 2011-11-16 Tom Tromey + * NEWS: Document ambiguous linespec change. + +2011-11-16 Tom Tromey + PR breakpoints/13105, PR objc/8341, PR objc/8343, PR objc/8366, PR objc/8535, PR breakpoints/11657, PR breakpoints/11970, PR breakpoints/12023, PR breakpoints/12334, PR breakpoints/12856, diff --git a/gdb/NEWS b/gdb/NEWS index c4e59c4..4605abd 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -3,6 +3,12 @@ *** Changes since GDB 7.3.1 +* GDB now handles ambiguous linespecs more consistently; the existing + FILE:LINE support has been expanded to other types of linespecs. A + breakpoint will now be set on all matching locations in all + inferiors, and locations will be added or removed according to + inferior changes. + * GDB now allows you to skip uninteresting functions and files when stepping with the "skip function" and "skip file" commands. diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 4975cd2..947a5d0 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2011-11-16 Tom Tromey + + * gdb.texinfo (Set Breaks): Update for new behavior. + 2011-11-15 Doug Evans * gdb.texinfo (Files): Document basenames-may-differ. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index f4f7f1e..1b01e19 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -3522,6 +3522,9 @@ in your program. Examples of this situation are: @itemize @bullet @item +Multiple functions in the program may have the same name. + +@item For a C@t{++} constructor, the @value{NGCC} compiler generates several instances of the function body, used in different cases. @@ -3535,11 +3538,7 @@ several places where that function is inlined. @end itemize In all those cases, @value{GDBN} will insert a breakpoint at all -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.}. +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 -- 1.7.6.4