This is the mail archive of the
mailing list for the GDB project.
Re: PATCH: new "void" memory region attribute
- From: Eli Zaretskii <eliz at is dot elta dot co dot il>
- To: gkm at kayak dot mcgary dot org
- Cc: gdb-patches at sources dot redhat dot com
- Date: Thu, 14 Feb 2002 12:23:52 +0200 (IST)
- Subject: Re: PATCH: new "void" memory region attribute
- References: <firstname.lastname@example.org>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> From: Greg McGary <email@example.com>
> Date: 13 Feb 2002 17:25:52 -0700
> --- gdb.texinfo 2002/02/08 00:39:45 1.89
> +++ gdb.texinfo 2002/02/14 00:17:32
> @@ -5642,6 +5642,8 @@ Memory is read only.
> Memory is write only.
> @item rw
> Memory is read/write. This is the default.
> +@item void
> +Memory is inaccessible.
> @end table
This part of the patch is approved, but please add a sentence to
explain what would be the effect of declaring a region `void' on GDB's
operation, from the user's point of view. It strikes me that this
text, from the beginning of your message:
> Add "void" attribute, which disallows both read & write access. This
> useful for guarding holes in a target's address space that cause the
> system to hang when read/written.
is exactly what would make this attribute's effect crystal-clear ;-)