This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH/RFC] Add back the 'info proc mappings' command.
Michael Snyder wrote:
>
> 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.
Oops, there's extra diffs in there. Please disregard the bits that
refer to "maint info sections".
> ------------------------------------------------------------------------
> 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