From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17729 invoked by alias); 3 Jun 2002 05:05:36 -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 17716 invoked from network); 3 Jun 2002 05:05:36 -0000 Received: from unknown (HELO rwcrmhc54.attbi.com) (216.148.227.87) by sources.redhat.com with SMTP; 3 Jun 2002 05:05:36 -0000 Received: from ocean.lucon.org ([12.234.143.38]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020603050535.SUFI13253.rwcrmhc54.attbi.com@ocean.lucon.org>; Mon, 3 Jun 2002 05:05:35 +0000 Received: by ocean.lucon.org (Postfix, from userid 1000) id D2A22125BB; Sun, 2 Jun 2002 22:05:34 -0700 (PDT) Date: Sun, 02 Jun 2002 22:05:00 -0000 From: "H . J . Lu" To: GDB , gcc@gcc.gnu.org Subject: Re: Does gdb 5.2 support gcc 3.1.1 on Linux/mips? Message-ID: <20020602220534.B17122@lucon.org> References: <20020602143627.A10506@lucon.org> <20020603010003.GA16363@branoic.them.org> <20020602194326.A14976@lucon.org> <20020603050101.GA18906@branoic.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020603050101.GA18906@branoic.them.org>; from drow@mvista.com on Mon, Jun 03, 2002 at 01:01:01AM -0400 X-SW-Source: 2002-06/txt/msg00014.txt.bz2 On Mon, Jun 03, 2002 at 01:01:01AM -0400, Daniel Jacobowitz wrote: > On Sun, Jun 02, 2002 at 07:43:26PM -0700, H . J . Lu wrote: > > On Sun, Jun 02, 2002 at 09:00:03PM -0400, Daniel Jacobowitz wrote: > > > On Sun, Jun 02, 2002 at 02:36:27PM -0700, H . J . Lu wrote: > > > > When I tried to debug gcc 3.1.1 on Linux/mips, I got > > > > > > > > # gdb xgcc > > > > GNU gdb 5.2-0.5 (5.2.0_2002-05-23-cvs) > > > > ... > > > > DW_FORM_strp pointing outside of .debug_str section > > > > > > > > gdb 5.2 works fine on Linux/x86 with gcc 3.1.1. Has anyone tried gdb > > > > 5.2 with gcc 3.1/3.2 running on any mips targets? > > > > > > My memory is hazy, but I believe this was a linker bug. Are you using > > > a current version of ld? > > > > > > > Yes. > > 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 H.J.