From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17434 invoked by alias); 24 Jul 2008 21:44:13 -0000 Received: (qmail 17425 invoked by uid 22791); 24 Jul 2008 21:44:12 -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 21:43:55 +0000 Received: from zps77.corp.google.com (zps77.corp.google.com [172.25.146.77]) by smtp-out.google.com with ESMTP id m6OLhliI003829 for ; Thu, 24 Jul 2008 22:43:48 +0100 Received: from an-out-0708.google.com (anab20.prod.google.com [10.100.53.20]) by zps77.corp.google.com with ESMTP id m6OLhM2f018489 for ; Thu, 24 Jul 2008 14:43:46 -0700 Received: by an-out-0708.google.com with SMTP id b20so635422ana.131 for ; Thu, 24 Jul 2008 14:43:46 -0700 (PDT) Received: by 10.100.33.11 with SMTP id g11mr1450545ang.26.1216935826498; Thu, 24 Jul 2008 14:43:46 -0700 (PDT) Received: by 10.151.107.3 with HTTP; Thu, 24 Jul 2008 14:43:46 -0700 (PDT) Message-ID: <8ac60eac0807241443w6466a0a8h776417b8644974b@mail.gmail.com> Date: Thu, 24 Jul 2008 21:49:00 -0000 From: "Paul Pluzhnikov" To: "Stan Shebs" Subject: Re: Address spaces Cc: "Doug Evans" , gdb@sourceware.org In-Reply-To: <4887CCF2.6020503@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4887C7BD.80601@earthlink.net> <4887CCF2.6020503@codesourcery.com> 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/msg00260.txt.bz2 On Wed, Jul 23, 2008 at 5:29 PM, Stan Shebs wrote: > Doug Evans wrote: >> It would be useful to have proper address spaces for non-multi-process >> situations 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. Here is another use case: I just spoke with someone who debugs a process on x86 which dynamically switches between "flat" 32-bit address space, and (possibly several) "restricted" 28-bit address sub-spaces (which are using CS, DS, and segment limits) in the same process. Think privileged and untrusted code mixed into the same process, with well-defined rules of transition between them. -- Paul Pluzhnikov