From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20543 invoked by alias); 3 Jun 2002 06:03:34 -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 20519 invoked from network); 3 Jun 2002 06:03:32 -0000 Received: from unknown (HELO rwcrmhc52.attbi.com) (216.148.227.88) by sources.redhat.com with SMTP; 3 Jun 2002 06:03:32 -0000 Received: from ocean.lucon.org ([12.234.143.38]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020603060332.RNPD2751.rwcrmhc52.attbi.com@ocean.lucon.org>; Mon, 3 Jun 2002 06:03:32 +0000 Received: by ocean.lucon.org (Postfix, from userid 1000) id 54AAC125BB; Sun, 2 Jun 2002 23:03:31 -0700 (PDT) Date: Sun, 02 Jun 2002 23:03:00 -0000 From: "H . J . Lu" To: GDB , gcc@gcc.gnu.org Cc: binutils@sources.redhat.com Subject: Re: Does gdb 5.2 support gcc 3.1.1 on Linux/mips? Message-ID: <20020602230331.A18107@lucon.org> References: <20020602143627.A10506@lucon.org> <20020603010003.GA16363@branoic.them.org> <20020602194326.A14976@lucon.org> <20020603050101.GA18906@branoic.them.org> <20020602220534.B17122@lucon.org> <20020603050906.GA19164@branoic.them.org> <20020602224240.A17723@lucon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020602224240.A17723@lucon.org>; from hjl@lucon.org on Sun, Jun 02, 2002 at 10:42:40PM -0700 X-SW-Source: 2002-06/txt/msg00017.txt.bz2 On Sun, Jun 02, 2002 at 10:42:40PM -0700, H . J . Lu wrote: > On Mon, Jun 03, 2002 at 01:09:06AM -0400, Daniel Jacobowitz wrote: > > > > > > > > Then could you check if the produced binary is incorrect? That error > > > > usually indicates linker error. > > > > > > Did you imply gdb 5.2 worked fine for you with gcc 3.1.1 running on > > > your mips platform? My Linux/mipsel gcc 3.1.1 seems to work ok > > > otherwise: > > > > > > http://gcc.gnu.org/ml/gcc-testresults/2002-06/msg00069.html > > > > I haven't tried it in a while, but 3.1 snapshots worked fine with 5.2 > > release, yes. > > > > I doubt it is a linker bug. I have a simple C file. I cross compiled > it to Linux/mipsel on Linux/x86 with gcc 3.1.1. I got > > # gcc -g ~/tmp/s.c -o ~/tmp/s > # gcc -g ~/tmp/s.c -o ~/tmp/s.o -c > # readelf -dw ~/tmp/s.o > /dev/null > unsupported or unknown DW_CFA_17 > # readelf -dw ~/tmp/s.o > /dev/null > unsupported or unknown DW_CFA_17 > # gdb ~/tmp/s > ... > DW_FORM_strp pointing outside of .debug_str section > > It looks like a gcc/gas bug to me. Can you tell me what you get with > your gdb and readelf on the enclosed s.o and s as well as what you get > with s and s.o compiled from s.c with your gcc 3.1 mips compiler? DW_CFA_17 is DW_CFA_offset_extended_sf, which was added to gcc on 2002-01-30. I have verifed that gcc 3.1.1 does generate it for mips. It looks like we have at least 2 bugs. First, readelf doesn't handle DW_CFA_offset_extended_sf and maybe other DAWRF debug info generated by gcc 3.1.1. Secondly, gdb 5.2 doesn't work with gcc 3.1.1 for Linux/mips. H.J.