From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-16553-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 14324 invoked by alias); 26 Jun 2002 20:00:54 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 14313 invoked from network); 26 Jun 2002 20:00:52 -0000
Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35)
  by sources.redhat.com with SMTP; 26 Jun 2002 20:00:52 -0000
Received: by zwingli.cygnus.com (Postfix, from userid 442)
	id E798A5EA11; Wed, 26 Jun 2002 15:00:50 -0500 (EST)
To: Don Howard <dhoward@redhat.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
	<gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] memattr bounds
References: <Pine.LNX.4.33.0206241458330.1658-100000@theotherone>
From: Jim Blandy <jimb@redhat.com>
Date: Wed, 26 Jun 2002 13:00:00 -0000
In-Reply-To: <Pine.LNX.4.33.0206241458330.1658-100000@theotherone>
Message-ID: <npofdx4xot.fsf@zwingli.cygnus.com>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2002-06/txt/msg00547.txt.bz2


Don Howard <dhoward@redhat.com> writes:
> Is the doco descriptive enough?  I'm trying to be brief without being
> terse...
> Index: doc/gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
> retrieving revision 1.102
> diff -p -u -w -r1.102 gdb.texinfo
> --- doc/gdb.texinfo	11 Jun 2002 20:36:57 -0000	1.102
> +++ doc/gdb.texinfo	24 Jun 2002 21:59:06 -0000
> @@ -5601,9 +5601,10 @@ to enable, disable, or remove a memory r
>  
>  @table @code
>  @kindex mem
> -@item mem @var{address1} @var{address2} @var{attributes}@dots{}
> -Define memory region bounded by @var{address1} and @var{address2}
> -with attributes @var{attributes}@dots{}.
> +@item mem @var{lower} @var{upper} @var{attributes}@dots{}
> +Define memory region bounded by @var{lower} and @var{upper} with
> +attributes @var{attributes}@dots{}.  Note that @var{upper} == 0 is a
> +special case: it indicates the max memory address.

Why try to be terse or brief?  This is the reference manual; it's more
important to be clear and complete, no?

Also, I don't think it's cool to use `==' in the reference manual;
it's supposed to be English.  :)

        As a special case, if @var{upper} is zero, then the memory
        region ends at the top of the address space.