aboutsummaryrefslogtreecommitdiff
path: root/binutils
diff options
context:
space:
mode:
authorTristan Gingold <tristan.gingold@adacore.com>2014-07-03 17:30:49 +0200
committerTristan Gingold <tristan.gingold@adacore.com>2014-07-03 17:31:45 +0200
commit8d112f9ecbe59b0eee3ec636a86891a6a82e4d9b (patch)
treea5f6708a167599c509a78d81e4fcfe3a397ff2ba /binutils
parent92c3b204c714996d00cb93afdbfed554ed58fef0 (diff)
downloadgdb-8d112f9ecbe59b0eee3ec636a86891a6a82e4d9b.zip
gdb-8d112f9ecbe59b0eee3ec636a86891a6a82e4d9b.tar.gz
gdb-8d112f9ecbe59b0eee3ec636a86891a6a82e4d9b.tar.bz2
Clarify doc on addr2line output.
binutils/ * doc/binutils.texi: Clarify addr2line output.
Diffstat (limited to 'binutils')
-rw-r--r--binutils/ChangeLog4
-rw-r--r--binutils/doc/binutils.texi41
2 files changed, 28 insertions, 17 deletions
diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index e81c97a..c5a5c20 100644
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,7 @@
+2014-07-03 Tristan Gingold <gingold@adacore.com>
+
+ * doc/binutils.texi: Clarify addr2line output.
+
2014-07-01 Alan Modra <amodra@gmail.com>
* objdump.c (dump_bfd_header): Don't print HAS_LOAD_PAGE.
diff --git a/binutils/doc/binutils.texi b/binutils/doc/binutils.texi
index b674b9d..3874f25 100644
--- a/binutils/doc/binutils.texi
+++ b/binutils/doc/binutils.texi
@@ -3214,26 +3214,33 @@ standard input, and prints the file name and line number for each
address on standard output. In this mode, @command{addr2line} may be used
in a pipe to convert dynamically chosen addresses.
-The format of the output is @samp{FILENAME:LINENO}. The file name and
-line number for each input address is printed on separate lines.
+The format of the output is @samp{FILENAME:LINENO}. By default
+each input address generates one line of output.
-If the @option{-f} option is used, then each @samp{FILENAME:LINENO}
-line is preceded by @samp{FUNCTIONNAME} which is the name of the
-function containing the address.
+Two options can generate additional lines before each
+@samp{FILENAME:LINENO} line (in that order).
+
+If the @option{-a} option is used then a line with the input address
+is displayed.
+
+If the @option{-f} option is used, then a line with the
+@samp{FUNCTIONNAME} is displayed. This is the name of the function
+containing the address.
+
+One option can generate additional lines after the
+@samp{FILENAME:LINENO} line.
If the @option{-i} option is used and the code at the given address is
-present there because of inlining by the compiler then the
-@samp{@{FUNCTIONNAME@} FILENAME:LINENO} information for the inlining
-function will be displayed afterwards. This continues recursively
-until there is no more inlining to report.
-
-If the @option{-a} option is used then the output is prefixed by the
-input address.
-
-If the @option{-p} option is used then the output for each input
-address is displayed on one, possibly quite long, line. If
-@option{-p} is not used then the output is broken up into multiple
-lines, based on the paragraphs above.
+present there because of inlining by the compiler then additional
+lines are displayed afterwards. One or two extra lines (if the
+@option{-f} option is used) are displayed for each inlined function.
+
+Alternatively if the @option{-p} option is used then each input
+address generates a single, long, output line containing the address,
+the function name, the file name and the line number. If the
+@option{-i} option has also been used then any inlined functions will
+be displayed in the same manner, but on separate lines, and prefixed
+by the text @samp{(inlined by)}.
If the file name or function name can not be determined,
@command{addr2line} will print two question marks in their place. If the