From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10181 invoked by alias); 26 Jul 2005 03:19:06 -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 10158 invoked by uid 22791); 26 Jul 2005 03:19:03 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 26 Jul 2005 03:19:03 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1DxFwG-0006o1-LB; Mon, 25 Jul 2005 23:17:04 -0400 Date: Tue, 26 Jul 2005 03:19:00 -0000 From: Daniel Jacobowitz To: Wu Zhou Cc: kamaraju@gmail.com, fortran@gcc.gnu.org, gdb@sources.redhat.com Subject: Re: gfortran - gdb problem Message-ID: <20050726031703.GA25841@nevyn.them.org> Mail-Followup-To: Wu Zhou , kamaraju@gmail.com, fortran@gcc.gnu.org, gdb@sources.redhat.com References: <20050725130929.GA2090@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-07/txt/msg00238.txt.bz2 On Sat, Jul 23, 2005 at 03:43:58AM +0800, Wu Zhou wrote: > My question here is: is it desirable to transfer the name to lower-case if > the language is case insensitive. My point is that the compiler could handle > this and GDB needs only to handle what we get from the compiler. Generally it's the other way round: GDB must cope with whatever strange things the compiler produces. > As for this case, I don't know how other case-insensitive languages behave. > But it might helps to change the conditional expression to: > > case_sensitivity == case_sensitive_off && current_language->la_language != language_fortran > > What do you think? If there is any error, please correct me. Thanks. No; adding checks specific to the language is almost always wrong. The only case insensitive languages in the GDB source tree are Scheme (and I don't think the Scheme support has worked in many years) and Fortran. So disabling it for Fortran is about the same as deleting the code entirely. Here's the original patch: http://sourceware.org/ml/gdb-patches/2000-08/msg00025.html Presumably, whatever HP Fortran compiler Jimmy Guo was trying to add support for always generated symbols in lowercase, so this was sufficient. gfortran doesn't. It appears to use case somewhat inconsistently. The fact is, our symbol table does not support case insensitive lookup. I suppose one cheap solution to this would be to lower case based on CU language when reading in the symbol table, but that's not a very pretty solution. Perhaps Elena (the symbol table maintainer) has another idea. -- Daniel Jacobowitz CodeSourcery, LLC