From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8403 invoked by alias); 3 Oct 2002 00:49:03 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 8394 invoked from network); 3 Oct 2002 00:49:02 -0000 Received: from unknown (HELO mail-out2.apple.com) (17.254.0.51) by sources.redhat.com with SMTP; 3 Oct 2002 00:49:02 -0000 Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.11.3/8.11.3) with ESMTP id g930n2s26542 for ; Wed, 2 Oct 2002 17:49:02 -0700 (PDT) Received: from scv1.apple.com (scv1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Wed, 2 Oct 2002 17:48:54 -0700 Received: from inghji.apple.com (inghji.apple.com [17.201.22.240]) by scv1.apple.com (8.11.3/8.11.3) with ESMTP id g930n2b29281 for ; Wed, 2 Oct 2002 17:49:02 -0700 (PDT) Date: Wed, 02 Oct 2002 17:49:00 -0000 Subject: Re: RFA: Search for symbol names the same way they're hashed. Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v543) From: Jim Ingham To: gdb-patches@sources.redhat.com Content-Transfer-Encoding: 7bit In-Reply-To: <1033595444.9324.ezmlm@sources.redhat.com> Message-Id: X-SW-Source: 2002-10/txt/msg00090.txt.bz2 On Wednesday, October 2, 2002, at 02:50 PM, gdb-patches-digest-help@sources.redhat.com wrote: >> We need to make demangling-style only affect *printout* and *user >> entered strings*, and during symbol reading, force it to auto, so it >> always gets the right names in the symbol table in the first place. > > Doesn't that sort of defeat the point of letting the user set > demangling style? It's in case something goes wrong with > autodetection.... > >>> The source code name of a symbol does not depend depend on the >>> current >>> demangling setting; >> >> And to enforce this, you have to make the readers *not* honor the >> demangling style. If you just fix SYMBOL_SOURCE_NAME, >> SYMBOL_INIT_DEMANGLED_NAME will still be only called once, and it'll >> have the wrong demangling style when it calls cplus_demangle, >> resulting >> in the symbol having the wrong demangled name forevermore. > > Perhaps we need to decide what the point of letting users force the > demangle style is, first. The case where we have had to use this was because we had private C++ API's in some of the Mac OS X frameworks for 10.2 (which was compiled with gcc 3.1) but users who didn't want to move their C++ code to 3.1 yet. When you hit the frameworks, gdb would see _Z, and assume the mangling style was the 3.1 style. Of course, all their code was 2.95, and they didn't in general care about the C++ stuff in frameworks (Apple tries not to export C++ API's if it can help it). So forcing demangling to 2.95 was useful in this case. This should, hopefully, be just a short term problem. Very few of our customers are still using 2.95 that we know about. But it is still worth keeping in mind for the next year or so... Jim -- Jim Ingham jingham@apple.com Developer Tools Apple Computer