Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: dje@google.com (Doug Evans)
To: pedro@codesourcery.com
Cc: gdb@sourceware.org
Subject: program spaces vs exec
Date: Wed, 05 Oct 2011 18:15:00 -0000	[thread overview]
Message-ID: <20111005181526.B6CCA2461D1@ruffy.mtv.corp.google.com> (raw)

Hi.

Question: Why does the program space remain unchanged across an exec?
[for reference sake, target = amd64-linux]

Is it just expediency?  Or is there a functional reason?

I ask because, for example, registering pretty-printers
with a particular progspace doesn't work as one would expect
in this case.  E.g., One needs the pretty-printers from the
previous program to be gone when the new one loads.

This concerns more than just exec of course.
E.g., Any time the "main" objfile is changed (e.g., "file foo") I'd intuitively
expect a new program space.

OTOH, it's entirely possible progspaces need to be looked at differently
for *nix.

For reference sake, from the archives I found this:
http://sourceware.org/ml/gdb-patches/2009-10/msg00110.html


             reply	other threads:[~2011-10-05 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 18:15 Doug Evans [this message]
2011-10-06 11:51 ` Pedro Alves
2011-10-06 18:23   ` Tom Tromey
2011-10-06 18:43     ` Pedro Alves
2011-10-06 19:32       ` Tom Tromey
2011-10-06 19:35       ` Tom Tromey
2011-10-06 19:41         ` Pedro Alves
2011-10-07 15:43           ` Tom Tromey
2011-10-09 20:42           ` Doug Evans
2011-10-06 19:05   ` Doug Evans
     [not found]   ` <CADPb22RCDS-a2FBm=Bf-W8j1X8CXatEFdZOpk1MAJyUHTvJvWA@mail.gmail.com>
2011-10-06 19:35     ` Pedro Alves

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=20111005181526.B6CCA2461D1@ruffy.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=pedro@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