From: Tom Tromey <tromey@redhat.com>
To: ali_anwar <ali_anwar@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
<gdb-patches@sourceware.org>, <keiths@redhat.com>
Subject: Re: warning: RTTI symbol not found for class
Date: Mon, 26 Nov 2012 19:23:00 -0000 [thread overview]
Message-ID: <87wqx8f9sq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <50B3BF10.7070508@codesourcery.com> (ali anwar's message of "Tue, 27 Nov 2012 00:12:16 +0500")
>>>>> "Ali" == ali anwar <ali_anwar@codesourcery.com> writes:
Ali> gdb -q ./cout -ex start -ex s -ex fin -ex c -ex q
Ali> [snip]
Ali> 2 int main () { std::cout << "foo" << std::endl; }
Ali> Value returned is $1 = warning: RTTI symbol not found for class
Ali> std::ostream'
What would be best is a recipe for recreating the bug that does not rely
on the system libstdc++ or its debuginfo or lack thereof.
Both this short test and the bs15503 test are exposed to the system
libraries in this way.
Tom
next prev parent reply other threads:[~2012-11-26 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 18:08 ali_anwar
2012-11-21 18:32 ` Jan Kratochvil
2012-11-26 19:14 ` ali_anwar
2012-11-26 19:23 ` Tom Tromey [this message]
2012-11-26 20:47 ` ali_anwar
2012-11-26 20:53 ` ali_anwar
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=87wqx8f9sq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ali_anwar@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=keiths@redhat.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