From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1175 invoked by alias); 5 Apr 2004 19:32:09 -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 986 invoked from network); 5 Apr 2004 19:31:59 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 5 Apr 2004 19:31:59 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1BAZpG-0000mh-5f; Mon, 05 Apr 2004 15:32:06 -0400 Date: Mon, 05 Apr 2004 19:32:00 -0000 From: Daniel Jacobowitz To: Michael Elizabeth Chastain , zack@codesourcery.com Cc: ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com Subject: Re: gcc HEAD, stabs+, TYPE_CODE_INT problem Message-ID: <20040405193205.GA2948@nevyn.them.org> Mail-Followup-To: Michael Elizabeth Chastain , zack@codesourcery.com, ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com References: <20040405190942.23D084B104@berman.michael-chastain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040405190942.23D084B104@berman.michael-chastain.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-04/txt/msg00029.txt.bz2 On Mon, Apr 05, 2004 at 03:09:42PM -0400, Michael Chastain wrote: > My last test run got stabbed really badly by a new problem > with gcc HEAD -gstabs+. There are about 700 new non-PASS results. > > The symptoms are: look at a global variable of type "char *". > > # gcc 3.3.3 > (gdb) ptype s > type = char * > > # gcc HEAD 2004-03-30 > (gdb) ptype s > type = * > > "invalid type code 7" is TYPE_CODE_INT. > > With gcc 3.3.3, the stabs look like this: > > # gcc 3.3.3 > .stabs "char:t(0,2)=r(0,2);0;127;",128,0,0,0 > .stabs "__caddr_t:t(7,35)=(7,36)=*(0,2)",128,0,82,0 > .stabs "s:G(7,36)",32,0,7,0 > > With gcc HEAD, the stabs look like this: > > # gcc HEAD > .stabs "__caddr_t:t(3,44)=(3,45)=*(3,46)=r(3,46);0;127;",128,0,82,0 > .stabs "s:G(3,45)",32,0,7,0 > > That is, gcc 3.3.3 emits a separate line for each primitive > type such as "char". gcc HEAD emits the definition of "char" > as a nested definition inside the first type that uses char, > such as pointer-to-char. > > The big question is: is this legal stabs? After reading > stabs.texinfo, I'm inclined to think that it is. > > If it's legal stabs, then someone has to enhance the stab reader. I > haven't started debugging gdb yet but I suspect that bit of code is > getting confused by the new-style nested definition. There's a bit of > code in read_range_type to recognize the special case of "char" as 0 to > 127, and gdb is behaving like that special-case isn't getting > recognized. If you debug further, I think you'll find that it is being recognized. The problem is probably that the type does not have a name; we're not emitting any debug information that associates the name 'char' with anything. Zack, any idea? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer