diff options
author | Andrew Burgess <andrew.burgess@embecosm.com> | 2018-02-16 15:37:05 +0000 |
---|---|---|
committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2018-02-19 20:15:18 +0000 |
commit | db1ae9c5b6660b22812d126c60778d5e298d2ea9 (patch) | |
tree | 414b68bf511b6632639765faa070d49b80b8dbf6 /gdb | |
parent | b248d650a44fb49d59a548ad173a3e60646159da (diff) | |
download | binutils-db1ae9c5b6660b22812d126c60778d5e298d2ea9.zip binutils-db1ae9c5b6660b22812d126c60778d5e298d2ea9.tar.gz binutils-db1ae9c5b6660b22812d126c60778d5e298d2ea9.tar.bz2 |
gdb/doc: Additional information about 'info line'
Extend the documentation of 'info line' command to:
1. Make 'info line' with no argument more obvious, and make it clearer
what this does.
2. Cover what happens when a secod 'info line' with no argument is
issued.
3. Extend the example output for 'info line ...' to include
symbolic addresses.
gdb/doc/ChangeLog:
* gdb.texinfo (Machine Code): Additional information about "info
line" command.
Diffstat (limited to 'gdb')
-rw-r--r-- | gdb/doc/ChangeLog | 5 | ||||
-rw-r--r-- | gdb/doc/gdb.texinfo | 19 |
2 files changed, 18 insertions, 6 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 375f24d..037173c 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2018-02-19 Andrew Burgess <andrew.burgess@embecosm.com> + + * gdb.texinfo (Machine Code): Additional information about "info + line" command. + 2018-01-15 Szabolcs Nagy <szabolcs.nagy@arm.com> * gdb.texinfo (gdb-add-index man): Add pindex. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 4ed5f6b..ee7adc8 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -8432,21 +8432,22 @@ well as hex. @table @code @kindex info line -@item info line @var{location} +@item info line +@itemx info line @var{location} Print the starting and ending addresses of the compiled code for source line @var{location}. You can specify source lines in any of -the ways documented in @ref{Specify Location}. +the ways documented in @ref{Specify Location}. With no @var{location} +information about the current source line is printed. @end table For example, we can use @code{info line} to discover the location of the object code for the first line of function @code{m4_changequote}: -@c FIXME: I think this example should also show the addresses in -@c symbolic form, as they usually would be displayed. @smallexample (@value{GDBP}) info line m4_changequote -Line 895 of "builtin.c" starts at pc 0x634c and ends at 0x6350. +Line 895 of "builtin.c" starts at pc 0x634c <m4_changequote> and \ + ends at 0x6350 <m4_changequote+4>. @end smallexample @noindent @@ -8455,7 +8456,8 @@ We can also inquire (using @code{*@var{addr}} as the form for @var{location}) what source line covers a particular address: @smallexample (@value{GDBP}) info line *0x63ff -Line 926 of "builtin.c" starts at pc 0x63e4 and ends at 0x6404. +Line 926 of "builtin.c" starts at pc 0x63e4 <m4_changequote+152> and \ + ends at 0x6404 <m4_changequote+184>. @end smallexample @cindex @code{$_} and @code{info line} @@ -8468,6 +8470,11 @@ sufficient to begin examining the machine code (@pxref{Memory, convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience Variables}). +@cindex info line, repeated calls +After @code{info line}, using @code{info line} again without +specifying a location will display information about the next source +line. + @table @code @kindex disassemble @cindex assembly instructions |