From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] Doc for "maint info sections" command
Date: Wed, 26 Dec 2001 11:17:00 -0000 [thread overview]
Message-ID: <200112261913.fBQJDiF26789@reddwarf.cygnus.com> (raw)
Eli,
I haven't tested this, and I'm not sure whether the @table operator
can be nested?
Michael
2001-12-26 Michael Snyder <msnyder@redhat.com>
* gdb.texinfo (maint info sections): Document.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.59
diff -c -3 -p -r1.59 gdb.texinfo
*** gdb.texinfo 2001/11/30 23:03:09 1.59
--- gdb.texinfo 2001/12/26 19:05:14
*************** use by @value{GDBN}, and the files from
*** 9347,9352 ****
--- 9347,9376 ----
command @code{help target} lists all possible targets rather than
current ones.
+ @kindex maint info sections
+ @item maint info sections
+ Another command that can give you extra information about program sections
+ is @code{maint info sections}. In addition to the section information
+ displayed by @code{info files}, this command displays the flags and file
+ offset of each section in the executable and core dump files. In addition,
+ @code{maint info sections} provides the following command options (which
+ may be arbitrarily combined):
+
+ @table @code
+ @kindex maint info sections ALLOBJ
+ @item ALLOBJ
+ Display sections for all loaded object files, including shared libraries.
+ @kindex maint info sections @samp{<section name(s)>}
+ @item @samp{<section name(s)>}
+ Display info only for section(s) matching the listed name(s).
+ @kindex maint info sections @samp{<section flag(s)>}
+ @item @samp{<section flag(s)>}
+ Display info only for sections for which @samp{<section flag(s)>} are true.
+ The section flags that @value{GDBN} currently knows about are @code{ALLOC,
+ LOAD, RELOC, READONLY, CODE, DATA, ROM, CONSTRUCTOR, HAS_CONTENTS,
+ NEVER_LOAD, COFF_SHARED_LIBRARY,} and @code{IS_COMMON}.
+ @end table
+
@end table
All file-specifying commands allow both absolute and relative file names
next reply other threads:[~2001-12-26 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 11:17 Michael Snyder [this message]
2001-12-27 0:48 ` Eli Zaretskii
2001-12-27 11:00 ` Michael Snyder
2001-12-27 11:31 ` Eli Zaretskii
2001-12-28 14:56 ` Michael Snyder
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=200112261913.fBQJDiF26789@reddwarf.cygnus.com \
--to=msnyder@cygnus.com \
--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