From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: program spaces vs exec
Date: Thu, 06 Oct 2011 18:23:00 -0000 [thread overview]
Message-ID: <m3r52qgett.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201110061251.22983.pedro@codesourcery.com> (Pedro Alves's message of "Thu, 6 Oct 2011 12:51:22 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> E.g., breakpoints are supposed to reset/resolve after the exec,
Pedro> and since the breakpoint symbol search scope is currently tied to
Pedro> a program space, keeping the same program space keeps that
Pedro> working the same.
FWIW, I'm changing this.
Pedro> For exec, I don't have a strong feeling either way, we could say
Pedro> that there's a new address/program space attached to the
Pedro> inferior, or we could say that the inferior's address/program
Pedro> spaces have been refreshed with a new set of pages. I chose the
Pedro> latter approach originally.
I think it would be fine to reset the pretty-printers at this point.
Pedro> How do pretty-printers from a shared library that unloads go
Pedro> away?
Generally they are attached to the objfile. So, they disappear
automatically when the objfile is removed.
Tom
next prev parent reply other threads:[~2011-10-06 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 18:15 Doug Evans
2011-10-06 11:51 ` Pedro Alves
2011-10-06 18:23 ` Tom Tromey [this message]
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=m3r52qgett.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=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