From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14681 invoked by alias); 1 Feb 2013 21:35:21 -0000 Received: (qmail 14291 invoked by uid 48); 1 Feb 2013 21:35:17 -0000 From: "tromey at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug symtab/12707] physname regression: set print demangle off Date: Fri, 01 Feb 2013 21:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Keywords: 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: 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/msg00163.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=12707 --- Comment #2 from Tom Tromey 2013-02-01 21:35:11 UTC --- The thread starts here: http://sourceware.org/ml/gdb-patches/2013-01/msg00287.html Jan is probably correct that we should store 3 forms for the template symbols in question: http://sourceware.org/ml/gdb-patches/2013-01/msg00381.html A more complicated approach is possible, based on checking the name-without-return-type, and then filtering the results. However this seems more difficult to get right. A third idea would be to introduce a kind of alias symbol that points to the "canonical" one. This might help avoid some data structures issues -- e.g., minsyms assume right now there can only be 2 names for a symbol, as minsyms only have 2 "next" pointers. -- 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.