From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-9105-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 4471 invoked by alias); 3 Jun 2002 06:30:26 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 4376 invoked from network); 3 Jun 2002 06:30:11 -0000
Received: from unknown (HELO sunsite.mff.cuni.cz) (195.113.19.66)
  by sources.redhat.com with SMTP; 3 Jun 2002 06:30:11 -0000
Received: (from jakub@localhost)
	by sunsite.mff.cuni.cz (8.11.6/8.11.6) id g536U2823776;
	Mon, 3 Jun 2002 08:30:02 +0200
Date: Sun, 02 Jun 2002 23:30:00 -0000
From: Jakub Jelinek <jakub@redhat.com>
To: "H . J . Lu" <hjl@lucon.org>, GDB <gdb@sources.redhat.com>,
   gcc@gcc.gnu.org
Subject: Re: Does gdb 5.2 support gcc 3.1.1 on Linux/mips?
Message-ID: <20020603083002.A20867@sunsite.ms.mff.cuni.cz>
Reply-To: Jakub Jelinek <jakub@redhat.com>
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.5.1i
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/msg00019.txt.bz2

On Mon, Jun 03, 2002 at 01:01:01AM -0400, Daniel Jacobowitz wrote:
> > > > # 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.

So far always when I saw this it was because of running gcc -S -g and then
running gcc -g on the resulting .s file (as --dwarf2 was passed to the
assembler, thus it basically had double debug info).

	Jakub