From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3624 invoked by alias); 14 Feb 2002 10:24:55 -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 3563 invoked from network); 14 Feb 2002 10:24:49 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 14 Feb 2002 10:24:49 -0000 Received: (from eliz@localhost) by is.elta.co.il (8.9.3/8.8.8) id MAA28658; Thu, 14 Feb 2002 12:23:52 +0200 (IST) Date: Thu, 14 Feb 2002 02:24:00 -0000 From: Eli Zaretskii Message-Id: <200202141023.MAA28658@is.elta.co.il> To: gkm@kayak.mcgary.org CC: gdb-patches@sources.redhat.com In-reply-to: (message from Greg McGary on 13 Feb 2002 17:25:52 -0700) Subject: Re: PATCH: new "void" memory region attribute Reply-to: Eli Zaretskii References: X-SW-Source: 2002-02/txt/msg00402.txt.bz2 > From: Greg McGary > 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 ;-)