public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/15175] New: can't find linker symbol for virtual table Date: Fri, 22 Feb 2013 18:24:00 -0000 [thread overview] Message-ID: <bug-15175-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15175 Bug #: 15175 Summary: can't find linker symbol for virtual table Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned@sourceware.org ReportedBy: tromey@redhat.com Classification: Unclassified I sometimes see the error "can't find linker symbol for virtual table". For example, with this program on F16: #include <typeinfo> #include <stdio.h> int main(int a, char *v[]) { const std::type_info *info = &typeid(main); printf ("%s\n", info->name()); } (gdb) start Temporary breakpoint 1 at 0x4005b3: file q.cc, line 6. Starting program: /tmp/q Temporary breakpoint 1, main (a=1, v=0x7fffffffe568) at q.cc:6 6 const std::type_info *info = &typeid(main); (gdb) n 8 printf ("%s\n", info->name()); (gdb) p info $1 = (warning: can't find linker symbol for virtual table for `std::type_info' value warning: can't find linker symbol for virtual table for `std::type_info' value const std::type_info *) 0x400720 -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-02-22 18:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-22 18:24 tromey at redhat dot com [this message] 2013-02-22 18:36 ` [Bug c++/15175] " tromey at redhat dot com 2013-02-22 21:49 ` tromey at redhat dot com
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-15175-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).