From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-39277-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 19573 invoked by alias); 30 May 2011 19:44:36 -0000
Received: (qmail 19563 invoked by uid 22791); 30 May 2011 19:44:36 -0000
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST
X-Spam-Check-By: sourceware.org
Received: from mail-fx0-f41.google.com (HELO mail-fx0-f41.google.com) (209.85.161.41)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 30 May 2011 19:44:16 +0000
Received: by fxm18 with SMTP id 18so3198401fxm.0        for <gdb@sourceware.org>; Mon, 30 May 2011 12:44:15 -0700 (PDT)
Received: by 10.223.161.194 with SMTP id s2mr215680fax.143.1306784655281; Mon, 30 May 2011 12:44:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.121.1 with HTTP; Mon, 30 May 2011 12:43:55 -0700 (PDT)
In-Reply-To: <BANLkTi=rs+62oeC3X5qV_C=HCRYrSTQpZg@mail.gmail.com>
References: <BANLkTi=rs+62oeC3X5qV_C=HCRYrSTQpZg@mail.gmail.com>
From: =?UTF-8?B?UGV0ciBIbHV6w61u?= <petr.hluzin@gmail.com>
Date: Mon, 30 May 2011 19:44:00 -0000
Message-ID: <BANLkTimO18hnvOGpbtEHUTUo0Nbpq0yxXg@mail.gmail.com>
Subject: Re: Addition of a special memory reading command
To: Tomas Martinec <fyzmat@gmail.com>
Cc: gdb@sourceware.org
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2011-05/txt/msg00138.txt.bz2

Hi Tomas

On 30 May 2011 18:04, Tomas Martinec <fyzmat@gmail.com> wrote:
>
> Probably I will be able to write a patch to gdb that implements the
> command. The patch would create the command and implement it in the
> remote protocol - for other targets it would just print "not
> supported".

GDB remote protocol already allows specifying some memory regions,
though you cannot specify a unreadable&unwritable "hole". The remote
command seems to be accesible as "info mem" command. See
http://sourceware.org/gdb/onlinedocs/gdb/Memory-Map-Format.html

Also there are "info proc mappings" not "info target", unfortunately
neither these are  exactly what you want.

I guess it would be useful to enhance these commands than implementing new ones.

-- 
Petr Hluzin