From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16420 invoked by alias); 24 Jul 2008 00:30:14 -0000 Received: (qmail 16395 invoked by uid 22791); 24 Jul 2008 00:30:13 -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; Thu, 24 Jul 2008 00:29:53 +0000 Received: (qmail 11559 invoked from network); 24 Jul 2008 00:29:51 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 24 Jul 2008 00:29:51 -0000 Message-ID: <4887CCF2.6020503@codesourcery.com> Date: Thu, 24 Jul 2008 06:15:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Doug Evans CC: gdb@sourceware.org Subject: Re: Address spaces References: <4887C7BD.80601@earthlink.net> In-Reply-To: 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/msg00251.txt.bz2 Doug Evans wrote: > It would be useful to have proper address spaces for non-multi-process > situations too. At the moment all one can do is hack in bits to > unused parts of the address (assuming such bits are available ...). > [I'm sure this isn't news. Just saying there are multiple reasons for > addresses being more than just the CORE_ADDR of today, and if we solve > one, let's at least consider the others too.] > Do you have some specific ideas in mind? Because I was assuming (and this is good to be aware of) that there would not be more than one address space associated with a process. (Instantly split I/D targets a la D10V come to mind, although that was handled by distinguishing pointers from addresses.) Stan > On Wed, Jul 23, 2008 at 5:07 PM, Stan Shebs wrote: > >> One of the recurring themes I'm noticing in my little bit of prototyping for >> multiprogram GDB is the need for a general concept of "address space". It's >> not quite the same as program/exec, because several programs could be in one >> address space in a non-virtual-memory system. It's not quite the same as >> process, because it applies to address lookup in execs prior to running any >> of them. It seems most like a tag glued on the front of a CORE_ADDR in fact >> (change CORE_ADDR to a struct? urgh). >> >> Anyway, I'm just throwing this out to get people's thoughts, and see if I'm >> missing an existing basic type or bit of infrastructure that could serve the >> purpose. I don't think address space objects would be user-visible, nor have >> very many properties; I think their main purpose in practice will be to keep >> target addresses in different execs and processes from getting mixed up with >> each other. >> >> Stan >> >> >> > >