From: Bob Rossi <bob@brasko.net>
To: gdb-patches@sources.redhat.com
Subject: -symbol-list-lines doco update
Date: Tue, 17 Feb 2004 15:43:00 -0000 [thread overview]
Message-ID: <20040217154339.GA5684@white> (raw)
This documents several of the special case's that -symbol-list-lines
outputs.
2004-02-17 Bob Rossi <bob@brasko.net>
* gdb.texinfo (-symbol-list-lines): Add info about the special
case's that this command outputs.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.195
diff -w -u -r1.195 gdb.texinfo
--- gdb.texinfo 17 Feb 2004 14:54:32 -0000 1.195
+++ gdb.texinfo 17 Feb 2004 15:35:21 -0000
@@ -17463,6 +17465,17 @@
addresses for the given source filename. The entries are sorted in
ascending PC order.
+There are two interesting points to be mentioned here.
+
+- The line number can be returned as "0". The line number "0" means
+end-of-sequence. For example, PCs greater than 0x8048406 that
+don't have a new starting line do not belong to this line number table.
+
+- Also, entries can be duplicated when returned. This means the front end
+must be capable of receiving several PC/line entries with the same value.
+Duplicated line numbers are emitted by the compiler to mark, mostly,
+the ends of prologues. Sometimes the prologue is zero-sized.
+
@subsubheading @value{GDBN} Command
There is no corresponding @value{GDBN} command.
@@ -17471,7 +17484,21 @@
@smallexample
(@value{GDBP})
-symbol-list-lines basics.c
-^done,lines=[@{pc="0x08048554",line="7"@},@{pc="0x0804855a",line="8"@}]
+^done,lines=[
+@{pc="0x080483e0",line="7"@},@{pc="0x080483e6",line="8"@},
+@{pc="0x080483ed",line="9"@},@{pc="0x080483f4",line="12"@},
+@{pc="0x08048400",line="13"@},@{pc="0x08048404",line="14"@},
+@{pc="0x08048404",line="14"@},@{pc="0x08048406",line="0"@},
+@{pc="0x08048408",line="16"@},@{pc="0x0804840e",line="17"@},
+@{pc="0x08048413",line="18"@},@{pc="0x08048415",line="0"@},
+@{pc="0x08048418",line="21"@},@{pc="0x0804841e",line="22"@},
+@{pc="0x0804842d",line="23"@},@{pc="0x0804842f",line="0"@},
+@{pc="0x08048430",line="26"@},@{pc="0x08048436",line="27"@},
+@{pc="0x08048449",line="28"@},@{pc="0x0804844b",line="0"@},
+@{pc="0x0804844c",line="31"@},@{pc="0x08048452",line="32"@},
+@{pc="0x0804846d",line="33"@},@{pc="0x08048488",line="35"@},
+@{pc="0x08048498",line="37"@},@{pc="0x0804849c",line="38"@},
+@{pc="0x0804849c",line="38"@},@{pc="0x080484a2",line="0"@}]
(@value{GDBP})
@end smallexample
next reply other threads:[~2004-02-17 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 15:43 Bob Rossi [this message]
2004-02-17 19:23 ` Eli Zaretskii
2004-02-17 19:50 ` Andrew Cagney
2004-02-17 20:54 ` Eli Zaretskii
2004-02-17 20:09 ` Bob Rossi
2004-02-17 20:46 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040217154339.GA5684@white \
--to=bob@brasko.net \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox