From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32410 invoked by alias); 25 Jul 2008 18:32:40 -0000 Received: (qmail 32401 invoked by uid 22791); 25 Jul 2008 18:32:40 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 25 Jul 2008 18:32:21 +0000 Received: (qmail 1569 invoked from network); 25 Jul 2008 18:32:19 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 25 Jul 2008 18:32:19 -0000 Message-ID: <488A1C2D.6020704@codesourcery.com> Date: Fri, 25 Jul 2008 18:50:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Ulrich Weigand CC: Stan Shebs , Doug Evans , gdb@sourceware.org Subject: Re: Address spaces References: <200807241827.m6OIRcJo010808@d12av02.megacenter.de.ibm.com> In-Reply-To: <200807241827.m6OIRcJo010808@d12av02.megacenter.de.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-07/txt/msg00272.txt.bz2 Ulrich Weigand wrote: > If you're interested into more details, I'll be happy to send you my > current patchset. > Thanks, I don't think I need them. > What does *not* work satisfactorily in all circumstances right now are user > interface issues. I don't want to expose the mangled CORE_ADDR to the user, > so the extra bits are stripped via gdbarch_addr_bits, and reinserted by the > gdbarch_integer_to_pointer family of functions, based on whether the currently > selected frame is SPU or PowerPC code. > > This makes it e.g. impossible to input a PowerPC address while in a SPU frame, > which would be useful occasionally. To do that right we'd have to expose a > user interface mechanism to select address spaces, though. > Between yours and Doug's and Paul's and Michael's examples :-) , I think it's pretty clear that we will want some kind of user interface. In the general case, a target can create arbitrarily-named address spaces, while in the conventional multiprogram case, address space names could simply be copied from exec names or process ids. Stan