Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Doc for "maint info sections" command
Date: Thu, 27 Dec 2001 11:00:00 -0000	[thread overview]
Message-ID: <3C2B6EE0.53B26DB@redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1011227104733.19068I-100000@is>

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

Eli Zaretskii wrote:
> 
> On Wed, 26 Dec 2001, Michael Snyder wrote:
> 
> > I haven't tested this, and I'm not sure whether the @table operator
> > can be nested?
> 
> Yes, @table can be nested.
> 
> > 2001-12-26  Michael Snyder  <msnyder@redhat.com>
> >
> >       * gdb.texinfo (maint info sections): Document.
> 
> Thanks for writing this up.  I have a few comments:

Great, thanks for the suggestions.  How's this?

[-- Attachment #2: allobj2.patch --]
[-- Type: text/plain, Size: 2446 bytes --]

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.60
diff -c -3 -p -r1.60 gdb.texinfo
*** gdb.texinfo	2001/12/27 18:41:40	1.60
--- gdb.texinfo	2001/12/27 18:59:21
*************** use by @value{GDBN}, and the files from 
*** 9347,9352 ****
--- 9347,9399 ----
  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
+ @item ALLOBJ
+ Display sections for all loaded object files, including shared libraries.
+ @item @var{sections}
+ Display info only for named var{sections}.
+ @item @var{section-flags}
+ Display info only for sections for which @var{section-flags} are true.
+ The section flags that @value{GDBN} currently knows about are:
+ @table @code
+ @item ALLOC
+ Section will have space allocated in the process when loaded.
+ Set for all sections except those containing debug information.
+ @item LOAD
+ Section will be loaded from the file into the child process memory.
+ Set for pre-initialized code and data, clear for .bss sections.
+ @item RELOC
+ Section needs to be relocated before loading.
+ @item READONLY
+ Section cannot be modified by the child process.
+ @item CODE
+ Section contains executable code only.
+ @tem DATA
+ Section contains data only (no executable code).
+ @item ROM
+ Section will reside in ROM.
+ @item CONSTRUCTOR
+ Section contains data for constructor/destructor lists.
+ @item HAS_CONTENTS
+ Section is not empty.
+ @item NEVER_LOAD
+ An instruction to the linker to not output the section.
+ @item COFF_SHARED_LIBRARY
+ A notification to the linker that the section contains
+ COFF shared library information.
+ @item IS_COMMON
+ Section contains common symbols.
+ @end table
+ @end table
  @end table
  
  All file-specifying commands allow both absolute and relative file names

  reply	other threads:[~2001-12-27 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-26 11:17 Michael Snyder
2001-12-27  0:48 ` Eli Zaretskii
2001-12-27 11:00   ` Michael Snyder [this message]
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=3C2B6EE0.53B26DB@redhat.com \
    --to=msnyder@redhat.com \
    --cc=eliz@is.elta.co.il \
    --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