From: Nick Roberts <nickrob@snap.net.nz>
To: gdb-patches@sourceware.org
Subject: [DOC:-file-list-exec-source-file]
Date: Wed, 30 Jan 2008 04:08:00 -0000 [thread overview]
Message-ID: <18335.63041.986587.622120@kahikatea.snap.net.nz> (raw)
This patch updates the manual to my recent change
to -file-list-exec-source-file.
OK to commit?
--
Nick http://www.inet.net.nz/~nickrob
2008-01-30 Nick Roberts <nickrob@snap.net.nz>
* gdb.texinfo (GDB/MI File Commands): Describe new output
field for MI command -file-list-exec-source-file.
*** gdb.texinfo.~1.462.~ 2008-01-30 14:25:13.000000000 +1300
--- gdb.texinfo 2008-01-30 16:56:00.000000000 +1300
*************** N.A.
*** 21035,21041 ****
@end smallexample
List the line number, the current source file, and the absolute path
! to the current source file for the current executable.
@subsubheading @value{GDBN} Command
--- 21035,21043 ----
@end smallexample
List the line number, the current source file, and the absolute path
! to the current source file for the current executable. The macro
! information field has a value of @samp{1} or @samp{0} depending on
! whether or not the file includes preprocessor macro information.
@subsubheading @value{GDBN} Command
*************** The @value{GDBN} equivalent is @samp{inf
*** 21046,21052 ****
@smallexample
(gdb)
123-file-list-exec-source-file
! 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c"
(gdb)
@end smallexample
--- 21048,21054 ----
@smallexample
(gdb)
123-file-list-exec-source-file
! 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c,macro-info="1"
(gdb)
@end smallexample
next reply other threads:[~2008-01-30 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 4:08 Nick Roberts [this message]
2008-01-30 4:20 ` [DOC:-file-list-exec-source-file] Eli Zaretskii
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=18335.63041.986587.622120@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sourceware.org \
/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