From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21804 invoked by alias); 22 Feb 2013 21:54:20 -0000 Received: (qmail 21781 invoked by uid 48); 22 Feb 2013 21:54:20 -0000 From: "tromey at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug c++/11990] "can't find linker symbol for virtual table for ..." when printing variables Date: Fri, 22 Feb 2013 21:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Keywords: archer X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Keywords Status Last reconfirmed Ever Confirmed Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2013-q1/txt/msg00306.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=11990 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |archer Status|UNCONFIRMED |NEW Last reconfirmed| |2013-02-22 Ever Confirmed|0 |1 --- Comment #3 from Tom Tromey 2013-02-22 21:54:18 UTC --- It seems possible to fix this with not much effort in gnu-v3-abi.c: (top-gdb) p vtable_symbol_name $1 = 0x0 (top-gdb) p *vtable_symbol $2 = { ginfo = { name = 0x21271d6 "_ZTVN10__cxxabiv120__function_type_infoE@@CXXABI_1.3", [...] We could do some demangling hackery here. But maybe it would be better to do this hackery when creating the symbol in the first place. -- 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.