From: Michael Snyder <msnyder@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] Add back the 'info proc mappings' command.
Date: Wed, 26 Dec 2001 11:27:00 -0000 [thread overview]
Message-ID: <3C2A23AD.5DE52878@cygnus.com> (raw)
In-Reply-To: <3C2A2270.CEE6B1F6@cygnus.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Michael Snyder wrote:
>
> Eli Zaretskii wrote:
> >
> > To: msnyder@cygnus.com
> > > From: Michael Snyder <msnyder@cygnus.com>
> > > Date: Fri, 21 Dec 2001 14:59:53 -0800 (PST)
> > >
> > > This adds back a sub-command ('mappings') of the "info proc"
> > > command, which was lost a couple years ago when procfs.c was
> > > rewritten.
> >
> > Thanks!
> >
> > Please consider writing this command's description for the manual.
>
> It's already there. In fact, the manual currently includes docs
> for several "info proc" options that no longer exist. Until someone
> finds the time to re-implement them, I suggest that these items
> be commented out or removed.
>
> I don't know how to comment out a section of a texinfo file.
> Do you?
Hmmm, here's an attempt. If you know a nicer way to comment out
a section, or if you'd prefer just to remove them until they're
needed, please let me know.
[-- Attachment #2: infoproc.patch --]
[-- Type: text/plain, Size: 3767 bytes --]
2001-12-26 Michael Snyder <msnyder@redhat.com>
* gdb.texinfo (info proc): Remove documentation for 'info proc'
sub-options that are currently not implemented.
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:25:05
*************** 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
*************** Summarize available information about th
*** 11259,11283 ****
@item info proc mappings
Report on the address ranges accessible in the program, with information
on whether your program may read, write, or execute each range.
!
! @kindex info proc times
! @item info proc times
! Starting time, user CPU time, and system CPU time for your program and
! its children.
!
! @kindex info proc id
! @item info proc id
! Report on the process IDs related to your program: its own process ID,
! the ID of its parent, the process group ID, and the session ID.
!
! @kindex info proc status
! @item info proc status
! General information on the state of the process. If the process is
! stopped, this report includes the reason for stopping, and any signal
! received.
!
! @item info proc all
! Show all the above information about the process.
@end table
@node DJGPP Native
--- 11283,11307 ----
@item info proc mappings
Report on the address ranges accessible in the program, with information
on whether your program may read, write, or execute each range.
! @comment
! @comment @kindex info proc times
! @comment @item info proc times
! @comment Starting time, user CPU time, and system CPU time for your program
! @comment and its children.
! @comment
! @comment @kindex info proc id
! @comment @item info proc id
! @comment Report on the process IDs related to your program: its own process ID,
! @comment the ID of its parent, the process group ID, and the session ID.
! @comment
! @comment @kindex info proc status
! @comment @item info proc status
! @comment General information on the state of the process. If the process is
! @comment stopped, this report includes the reason for stopping, and any signal
! @comment received.
! @comment
! @comment @item info proc all
! @comment Show all the above information about the process.
@end table
@node DJGPP Native
next prev parent reply other threads:[~2001-12-26 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 15:00 Michael Snyder
2001-12-23 4:13 ` Eli Zaretskii
2001-12-26 11:22 ` Michael Snyder
2001-12-26 11:27 ` Michael Snyder [this message]
2001-12-26 11:34 ` Michael Snyder
2001-12-26 12:29 ` Eli Zaretskii
2001-12-26 14:28 ` Michael Snyder
2001-12-27 0:49 ` Eli Zaretskii
2001-12-27 10:43 ` Michael Snyder
2001-12-29 11:17 ` Andrew Cagney
2001-12-23 13:12 ` Daniel Jacobowitz
2001-12-28 11:48 ` 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=3C2A23AD.5DE52878@cygnus.com \
--to=msnyder@cygnus.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