Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Paul Pluzhnikov" <ppluzhnikov@google.com>
To: "Stan Shebs" <stan@codesourcery.com>
Cc: "Doug Evans" <dje@google.com>, gdb@sourceware.org
Subject: Re: Address spaces
Date: Thu, 24 Jul 2008 21:49:00 -0000	[thread overview]
Message-ID: <8ac60eac0807241443w6466a0a8h776417b8644974b@mail.gmail.com> (raw)
In-Reply-To: <4887CCF2.6020503@codesourcery.com>

On Wed, Jul 23, 2008 at 5:29 PM, Stan Shebs <stan@codesourcery.com> 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


  parent reply	other threads:[~2008-07-24 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24  0:14 Stan Shebs
2008-07-24  0:30 ` Doug Evans
2008-07-24  6:15   ` Stan Shebs
2008-07-24 15:56     ` Ulrich Weigand
2008-07-24 18:17       ` Stan Shebs
2008-07-24 18:28         ` Doug Evans
2008-07-25  5:52           ` Michael Snyder
2008-07-25  8:50           ` Jeremy Bennett
2008-07-24 20:31         ` Ulrich Weigand
2008-07-25 18:50           ` Stan Shebs
2008-07-25  3:31       ` Michael Snyder
2008-07-24 21:49     ` Paul Pluzhnikov [this message]
2008-07-25  3:29     ` Michael Snyder
2008-07-25 18:32       ` Stan Shebs
2008-07-25 19:13         ` Mark Kettenis
2008-07-25 19:24           ` Stan Shebs
2008-07-31 18:43 ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ac60eac0807241443w6466a0a8h776417b8644974b@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=stan@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox