This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: undefined virtual table references in 2.12 and later
> > >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