Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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 13:19:00 -0000	[thread overview]
Message-ID: <20071213131841.GA24646@caradoc.them.org> (raw)
In-Reply-To: <e394668d0712130016t70af7e4dgefa188b07907d8b@mail.gmail.com>

On Thu, Dec 13, 2007 at 12:16:36AM -0800, Doug Evans wrote:
> What happens if TYPE_OBJFILE (type) != TYPE_OBJFILE
> (TYPE_VPTR_BASETYPE (baseclass)) ?

Precisely what you saw, but how does this happen?  The baseclass links
should normally point through to other types in the same objfile.

I'm guessing that there was inadequate debug info for a base class,
leading GDB to do name resolution into a shared library with better
debug info (probably because it defined the class's key method)?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-12-13 13:19 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
2007-12-13  8:16   ` Doug Evans
2007-12-13 13:19     ` Daniel Jacobowitz [this message]
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=20071213131841.GA24646@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