From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: gdb@sourceware.org
Subject: Re: protection from dangling pointers in dwarf info when .so's go away
Date: Thu, 13 Dec 2007 03:27:00 -0000 [thread overview]
Message-ID: <20071213032724.GA25868@caradoc.them.org> (raw)
In-Reply-To: <e394668d0712121757q7f0dd552p4d36ee8f035bff30@mail.gmail.com>
On Wed, Dec 12, 2007 at 05:57:58PM -0800, Doug Evans wrote:
> Is it the case that vptr_basetype for myclass should never have gotten
> assigned a value pointing into a .so (or any other obstack)?
Sounds likely to me, but may not be practical.
> Or is
> gdb supposed to have cleaned up after itself when the .so data got
> freed?
We do this for user variables when their objfile goes away, by
recursively copying their type. We don't walk types from other
objfiles looking for pointers, so there really shouldn't be any.
> Or something else? Any guidance on where the fix should go is
> appreciated. I suppose an easy solution is to toss out all info, not
> just for .so's, though that will slow down re-runs.
No, that's impossible. Remember dlopen and dlclose.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-13 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 1:58 Doug Evans
2007-12-13 3:27 ` Daniel Jacobowitz [this message]
2007-12-13 8:16 ` Doug Evans
2007-12-13 13:19 ` Daniel Jacobowitz
2007-12-13 16:56 ` Jim Blandy
2007-12-14 0:04 ` Doug Evans
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=20071213032724.GA25868@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
/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