public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/64670] New: -fsanitize=vptr leads to "undefined reference to `typeinfo for class'"
Date: Mon, 19 Jan 2015 15:32:00 -0000	[thread overview]
Message-ID: <bug-64670-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64670

            Bug ID: 64670
           Summary: -fsanitize=vptr leads to "undefined reference to
                    `typeinfo for class'"
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org

I have a class of the form
  class name {
    virtual ~name() {};
    virtual void func() = 0;
  };

Using -fsanitize=vptr leads to an "undefined reference to `typeinfo for name'".

I'll try to come up with a test case.


             reply	other threads:[~2015-01-19 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 15:32 burnus at gcc dot gnu.org [this message]
2015-01-19 15:58 ` [Bug sanitizer/64670] " burnus at gcc dot gnu.org
2015-01-19 16:07 ` mpolacek at gcc dot gnu.org
2015-01-19 16:14 ` jakub at gcc dot gnu.org
2015-01-29 15:52 ` jason at gcc dot gnu.org
2015-01-30 13:15 ` burnus at gcc dot gnu.org
2015-02-09 16:42 ` burnus at gcc dot gnu.org
2015-02-09 22:00 ` jason at gcc dot gnu.org
2015-02-10  8:09 ` burnus at gcc dot gnu.org
2015-02-10 16:23 ` jason at gcc dot gnu.org
2015-02-10 16:26 ` burnus at gcc dot gnu.org
2015-02-10 16:32 ` jason at gcc dot gnu.org
2015-02-10 16:50 ` burnus at gcc dot gnu.org

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=bug-64670-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).