From: "Donald Zoch" <donald.zoch@amd.com>
To: binutils@sources.redhat.com, donald.zoch@amd.com
Subject: Re: undefined virtual table references in 2.12 and later
Date: Wed, 28 May 2003 19:23:00 -0000 [thread overview]
Message-ID: <20030528141559.D2266@lard.amd.com> (raw)
In-Reply-To: <m37k8ax5ly.fsf@gossamer.airs.com>
> > >From what I can tell though, in my libgcc.a (I'm using gcc 2.95.3),
> > the symbols are defined as weak objects, but then undefined several
> > times also:
> >
> > 00000000 V bad_exception virtual table
> > 00000000 V exception virtual table
> > U exception virtual table
> > U exception virtual table
> > U exception virtual table
>
> Note that several different symbol names can be demangled into
> ``... virtual table''. You should double check the real symbol names,
> to make sure this isn't some sort of weird situation in which
> different mangling is being used in different places.
>
> nm demangles by default; the --no-demangle option turns it off.
Thanks, but I did double check the real symbol names. The above
symbol, exception virtual table appears mangled as __vt_9exception
both in one of the objects that it's undefined in
libgcc.a:tinfo.o: U exception virtual table
with --no-demangle:
libgcc.a:tinfo.o: U __vt_9exception
and it appears as
libgcc.a:exception.o:00000000 V exception virtual table
with --no-demangle:
libgcc.a:exception.o:00000000 V __vt_9exception
Donald
----
Donald Zoch 5900 E. Ben White Blvd. MS 625
Advanced Micro Devices Austin, Tx 78741
MPD Unix Systems Administrator Phone: (512) 602-7945
donald.zoch@amd.com Pager: (512) 604-5401
next prev parent reply other threads:[~2003-05-28 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 18:55 Donald Zoch
2003-05-28 19:01 ` Ian Lance Taylor
2003-05-28 19:23 ` Donald Zoch [this message]
2003-05-28 19:27 ` Ian Lance Taylor
2003-05-28 22:01 ` H. J. Lu
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=20030528141559.D2266@lard.amd.com \
--to=donald.zoch@amd.com \
--cc=binutils@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).