From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6932 invoked by alias); 13 Mar 2003 20:54:22 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6918 invoked from network); 13 Mar 2003 20:54:22 -0000 Received: from unknown (HELO jackfruit.Stanford.EDU) (171.64.38.136) by sources.redhat.com with SMTP; 13 Mar 2003 20:54:22 -0000 Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h2DKsLY27334; Thu, 13 Mar 2003 12:54:21 -0800 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: gdb Cc: Tom Tromey , Michael Elizabeth Chastain Subject: Re: break jmisc.main References: From: David Carlton Date: Thu, 13 Mar 2003 20:54:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-03/txt/msg00212.txt.bz2 On 13 Mar 2003 12:39:03 -0800, David Carlton said: > So my guess is that, somewhere, a demangler is getting > called in a situation where the symbol isn't yet identified as a > Java symbol, so the C++ demangler gets used. Do the minsym readers > reliably know the language of the minsyms they're creating? If > not, then we could be getting the bad value there and caching it > with the new demangling code, so the bad value remains when the > symbol table is setting the symbol's name. To be specific, in prim_record_minimal_symbol_and_info, we see: SYMBOL_LANGUAGE (msymbol) = language_auto; SYMBOL_SET_NAMES (msymbol, (char *)name, strlen (name), objfile); Oops. David Carlton carlton@math.stanford.edu