From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27732 invoked by alias); 26 Nov 2012 19:23:30 -0000 Received: (qmail 27722 invoked by uid 22791); 26 Nov 2012 19:23:30 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Nov 2012 19:23:20 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qAQJNIUs027293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 26 Nov 2012 14:23:18 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id qAQJNHBC024121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 26 Nov 2012 14:23:18 -0500 From: Tom Tromey To: ali_anwar Cc: Jan Kratochvil , , Subject: Re: warning: RTTI symbol not found for class References: <50AD181E.1050607@codesourcery.com> <20121121183212.GA30560@host2.jankratochvil.net> <50B3BF10.7070508@codesourcery.com> Date: Mon, 26 Nov 2012 19:23:00 -0000 In-Reply-To: <50B3BF10.7070508@codesourcery.com> (ali anwar's message of "Tue, 27 Nov 2012 00:12:16 +0500") Message-ID: <87wqx8f9sq.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00685.txt.bz2 >>>>> "Ali" == ali anwar 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