From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11140 invoked by alias); 24 Jul 2008 00:14:44 -0000 Received: (qmail 11131 invoked by uid 22791); 24 Jul 2008 00:14:43 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 24 Jul 2008 00:14:16 +0000 Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id m6O0EBDY020109 for ; Thu, 24 Jul 2008 01:14:11 +0100 Received: from rv-out-0506.google.com (rvfb25.prod.google.com [10.140.179.25]) by wpaz5.hot.corp.google.com with ESMTP id m6O0Dc3g025818 for ; Wed, 23 Jul 2008 17:14:10 -0700 Received: by rv-out-0506.google.com with SMTP id b25so3472974rvf.37 for ; Wed, 23 Jul 2008 17:14:10 -0700 (PDT) Received: by 10.141.123.4 with SMTP id a4mr128841rvn.172.1216858450094; Wed, 23 Jul 2008 17:14:10 -0700 (PDT) Received: by 10.140.201.10 with HTTP; Wed, 23 Jul 2008 17:14:10 -0700 (PDT) Message-ID: Date: Thu, 24 Jul 2008 00:30:00 -0000 From: "Doug Evans" To: "Stan Shebs" Subject: Re: Address spaces Cc: gdb@sourceware.org In-Reply-To: <4887C7BD.80601@earthlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4887C7BD.80601@earthlink.net> X-IsSubscribed: yes 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/msg00250.txt.bz2 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.] 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 > >