public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: "Donald Zoch" <donald.zoch@amd.com>
Cc: binutils@sources.redhat.com
Subject: Re: undefined virtual table references in 2.12 and later
Date: Wed, 28 May 2003 19:27:00 -0000	[thread overview]
Message-ID: <m31xyix4do.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20030528141559.D2266@lard.amd.com>

"Donald Zoch" <donald.zoch@amd.com> writes:

> 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

Hmmm, from your original message:

> /u/zochd/build2/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/libgcc.a(exception.o):
> In function `__check_eh_spec':
> /u/zochd/gcc-2.95.3/build2/gcc/include/exception:15: undefined
> reference to `exception virtual table'

This error message says that exception.o has an undefined reference to
`exception virtual table'.  The above nm output says that exception.o
defines `exception virtual table' as a weak symbol.  In other words,
you are getting an undefined reference from an object which actually
defines the symbol.

I can not explain that.

Ian

  reply	other threads:[~2003-05-28 19:23 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
2003-05-28 19:27     ` Ian Lance Taylor [this message]
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=m31xyix4do.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=binutils@sources.redhat.com \
    --cc=donald.zoch@amd.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).