From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18647 invoked by alias); 29 Oct 2003 06:16:28 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18590 invoked from network); 29 Oct 2003 06:16:23 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 29 Oct 2003 06:16:23 -0000 Received: by zenia.home (Postfix, from userid 5433) id A2ADC207AF; Wed, 29 Oct 2003 01:15:24 -0500 (EST) To: gdb@sources.redhat.com Subject: Re: FW: Targeting dual Harvard architectures References: From: Jim Blandy Date: Wed, 29 Oct 2003 06:16:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-10/txt/msg00318.txt.bz2 Jim Blandy writes: > "Ken Dyck" writes: > > 1. Is it possible to modify gdb to support architectures with multiple > > memory spaces in a "user friendly" way (where "user friendly" is > > something like what David Taylor described in > > http://sources.redhat.com/ml/gdb/2001-02/msg00090.html)? So far my > > impression is yes. > > Yes --- with the understanding that it's restricted to just distinct > code and data spaces at the moment --- you can say: > > x/i (@code char *) 0x1234 > x/i (@data char *) 0x1234 > > and it'll do the right thing, if you define the ADDRESS_TO_POINTER and > POINTER_TO_ADDRESS methods appropriately. > > (Hey, this isn't in the GDB manual anywhere!) I've filed a bug about this.