From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26494 invoked by alias); 25 Jun 2002 07:23:51 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26482 invoked from network); 25 Jun 2002 07:23:48 -0000 Received: from unknown (HELO potter.sfbay.redhat.com) (205.180.83.107) by sources.redhat.com with SMTP; 25 Jun 2002 07:23:48 -0000 Received: from theotherone.redhat-remotie.org (IDENT:5NOyrZzHD8t7McHRt8ygrkHeAglCdg4x@romulus.sfbay.redhat.com [172.16.27.251]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g5P7PFQ14008 for ; Tue, 25 Jun 2002 00:25:15 -0700 Received: from localhost (localhost.fidalgo.net [127.0.0.1]) by theotherone.redhat-remotie.org (Postfix) with ESMTP id 54444BB40F; Tue, 25 Jun 2002 00:24:09 -0700 (PDT) Date: Tue, 25 Jun 2002 00:23:00 -0000 From: Don Howard X-X-Sender: To: Eli Zaretskii Cc: Subject: Re: [PATCH] memattr bounds In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-06/txt/msg00508.txt.bz2 On Tue, 25 Jun 2002, Eli Zaretskii wrote: > > On Mon, 24 Jun 2002, Don Howard wrote: > > > Is the doco descriptive enough? I'm trying to be brief without being > > terse... > > It's okay, but please say a word ore two about what "max memory address" > means. > > Otherwise, approved. > > Thanks. > I've checked in the following. Hopefully it describes "max memory address" better. If not, let me know. 2002-06-25 Don Howard * gdb.texinfo (Memory Region Attributes): Document new behavior for 'mem' command. 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 25 Jun 2002 07:18:31 -0000 @@ -5601,9 +5601,11 @@ 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 is treated as the the target's maximum memory address. +(0xffff on 16 bit targets, 0xffffffff on 32 bit targets, etc.) -- dhoward@redhat.com gdb engineering