public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vz-gdb at zeitlins dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/9541] Bogus "warning: can't find linker symbol for virtual table for 'Foo' value" messages
Date: Wed, 28 Nov 2012 19:26:00 -0000 [thread overview]
Message-ID: <bug-9541-4717-c4M2lV78RL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9541-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=9541
--- Comment #2 from vz-gdb at zeitlins dot org 2012-11-28 19:26:13 UTC ---
(In reply to comment #1)
> This has been reported before but never with a test case.
> I don't know how to reproduce it.
Unfortunately me neither. I've never seen it in small test applications.
> Does it still fail with a newer gdb?
> If so can you make a small test case?
I've seen it just recently with 7.2.50.20100904-cvs (still Debian, x86-64,
using wxWidgets shared libraries) and I can retest it with a later version if
it can help, but I unfortunately have no idea how to reproduce this in a simple
test case. Please let me know if you'd like me to test with the latest gdb
nevertheless.
--
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 prev parent reply other threads:[~2012-11-28 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9541-4717@http.sourceware.org/bugzilla/>
2012-11-28 17:43 ` tromey at redhat dot com
2012-11-28 19:26 ` vz-gdb at zeitlins dot org [this message]
2012-11-28 20:22 ` tromey at redhat dot com
2012-11-29 20:03 ` vz-gdb at zeitlins dot org
2013-03-06 20:05 ` 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-9541-4717-c4M2lV78RL@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: 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).