[PATCH 3/3] MI: document the format for breakpoints with multiple locations

[Mircea Gherzan <mircea dot gherzan at intel dot com>]

2013-02-28  Mircea Gherzan  <mircea.gherzan@intel.com>

gdb/doc:
	* gdb.texinfo (GDB/MI Breakpoint Information): Add a description
	and an example for the locations field.

Signed-off-by: Mircea Gherzan <mircea.gherzan@intel.com>
---
 gdb/doc/gdb.texinfo |   19 +++++++++++++++++++
 1 files changed, 19 insertions(+), 0 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 5f39d2e..d75b1af 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -28140,6 +28140,11 @@ This field is only given for tracepoints.  This is either @samp{y},
 meaning that the tracepoint is installed, or @samp{n}, meaning that it
 is not.
 
+@item locations
+This field is only given for breakpoints with multiple locations.  It is
+a list of breakpoint tuples with actual addresses and line information,
+one tuple for every location of the breakpoint.
+
 @item what
 Some extra data, the exact contents of which are type-dependent.
 
@@ -28157,6 +28162,20 @@ For example, here is what the output of @code{-break-insert}
 <- (gdb)
 @end smallexample
 
+For a breakpoint with multiple locations:
+
+@smallexample
+-> -break-insert foo
+<- ^done,bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
+    addr="<MULTIPLE>",times="0",original-location="foo",
+    locations=[@{number="2.1",enabled="y",addr="0x00000000004005a8",
+    func="foo()",file="overloaded.cc",fullname="/home/mircea/overloaded.cc",
+    line="25",thread-groups=["i1"]@},@{number="2.2",enabled="y",
+    addr="0x00000000004005ba",func="foo(int)",file="overloaded.cc",
+    fullname="/home/mircea/overloaded.cc",line="31",thread-groups=["i1"]@}]@}
+<-  (gdb)
+@end smallexample
+
 @node GDB/MI Frame Information
 @subsection @sc{gdb/mi} Frame Information
 
-- 
1.7.1