This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH] memattr bounds
- From: Don Howard <dhoward at redhat dot com>
- To: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Cc: <gdb-patches at sources dot redhat dot com>
- Date: Tue, 25 Jun 2002 00:24:09 -0700 (PDT)
- Subject: Re: [PATCH] memattr bounds
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 <dhoward@redhat.com>
* 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