From: Pedro Alves <pedro@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: program spaces vs exec
Date: Thu, 06 Oct 2011 19:41:00 -0000 [thread overview]
Message-ID: <201110062041.09462.pedro@codesourcery.com> (raw)
In-Reply-To: <m3mxddgbhj.fsf@fleche.redhat.com>
On Thursday 06 October 2011 20:34:48, Tom Tromey wrote:
> Forgot to reply to part...
>
> Pedro> How do pretty-printers from a shared library that unloads go
> Pedro> away?
>
> Tom> Generally they are attached to the objfile. So, they disappear
> Tom> automatically when the objfile is removed.
>
> Pedro> There must be something more to the issue then. Both "file foo" or
> Pedro> an exec get rid of the previous executable's symfile_objfile and
> Pedro> create a new one too, so the executable's printers must already be
> Pedro> being removed.
>
> That would work if the printer was attached to the executable's objfile;
> but you can also attach a printer to a program space, which is the
> problem case.
Then this isn't just about execs indeed, and I don't understand
the usefulness of attaching a printer to the program space.
The program space is the same even if you run -> kill -> run -> `attach to some
other process running some other program' -> kill -> "target remote :9999" ->
etc.
--
Pedro Alves
next prev parent reply other threads:[~2011-10-06 19:41 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
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 [this message]
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=201110062041.09462.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.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