From: Daniel Jacobowitz <drow@false.org>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb crash when printing C++ class
Date: Fri, 10 Dec 2004 21:46:00 -0000 [thread overview]
Message-ID: <20041210214640.GA20905@nevyn.them.org> (raw)
In-Reply-To: <41BA1487.8030302@qnx.com>
On Fri, Dec 10, 2004 at 04:26:31PM -0500, Kris Warkentin wrote:
> I compared the vptr entries in the readelf -wi output from gcc vs. icc
> and they're certainly different. I don't have enough understanding yet
> to know what differences are signifigant but hopefully looking at the
> dwarf2 reader will enlighten me. I've attached the readelf output just
> in case someone wants to take a look for anything obvious. Thanks.
GNU's use of DW_AT_containing_type for this is somewhat nonstandard.
You'll have to find another way to work out where the vptr is for the
ICC output. You may want to do it by the C++ ABI rather than by the
debug info.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-12-10 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 20:00 Kris Warkentin
2004-12-10 20:21 ` Daniel Jacobowitz
2004-12-10 21:44 ` Kris Warkentin
[not found] ` <41BA1487.8030302@qnx.com>
2004-12-10 21:46 ` Daniel Jacobowitz [this message]
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=20041210214640.GA20905@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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