Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] Add back the 'info proc mappings' command.
Date: Wed, 26 Dec 2001 14:28:00 -0000	[thread overview]
Message-ID: <3C2A4E05.276BA97D@cygnus.com> (raw)
In-Reply-To: <9427-Wed26Dec2001222739+0200-eliz@is.elta.co.il>

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

Eli Zaretskii wrote:
> 
> > Date: Wed, 26 Dec 2001 11:18:08 -0800
> > From: Michael Snyder <msnyder@cygnus.com>
> >
> > I don't know how to comment out a section of a texinfo file.
> 
> Put "@ignore..@end ignore" around the part you want to comment out.

Ah, OK -- how's this?

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

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 20:51:35
2001-12-26  Michael Snyder  <msnyder@redhat.com>

	* gdb.texinfo (info proc): Remove documentation for 'info proc'
	sub-options that are currently not implemented.

*************** Summarize available information about th
*** 11259,11265 ****
  @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
--- 11283,11289 ----
  @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.
! @ignore
  @kindex info proc times
  @item info proc times
  Starting time, user CPU time, and system CPU time for your program and
*************** received.
*** 11278,11283 ****
--- 11302,11308 ----
  
  @item info proc all
  Show all the above information about the process.
+ @end ignore
  @end table
  
  @node DJGPP Native

  reply	other threads:[~2001-12-26 22:28 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
2001-12-26 11:34       ` Michael Snyder
2001-12-26 12:29     ` Eli Zaretskii
2001-12-26 14:28       ` Michael Snyder [this message]
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=3C2A4E05.276BA97D@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