From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20385-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 12457 invoked by alias); 22 Dec 2004 18:25:07 -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 12285 invoked from network); 22 Dec 2004 18:24:51 -0000
Received: from unknown (HELO sccrmhc13.comcast.net) (204.127.202.64)
  by sourceware.org with SMTP; 22 Dec 2004 18:24:51 -0000
Received: from lucon.org ([24.6.212.230]) by comcast.net (sccrmhc13) with ESMTP
          id <20041222182450016003lv9ke>; Wed, 22 Dec 2004 18:24:50 +0000
Received: by lucon.org (Postfix, from userid 1000)
	id CBC2263DD3; Wed, 22 Dec 2004 10:24:49 -0800 (PST)
Date: Wed, 22 Dec 2004 18:25:00 -0000
From: "H. J. Lu" <hjl@lucon.org>
To: Nick Clifton <nickc@redhat.com>
Cc: gcc@gcc.gnu.org, GDB <gdb@sources.redhat.com>,
	binutils@sources.redhat.com
Subject: Re: Is this a gcc, gdb or readelf bug?
Message-ID: <20041222182449.GA29407@lucon.org>
References: <20041222011627.GA15293@lucon.org> <41C9577D.3010509@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41C9577D.3010509@redhat.com>
User-Agent: Mutt/1.4.1i
X-SW-Source: 2004-12/txt/msg00110.txt.bz2

On Wed, Dec 22, 2004 at 11:16:13AM +0000, Nick Clifton wrote:
> Hi H. J.
> 
> >I can't debug gcc 4.0 with gdb:
> >
> >http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124
> 
> Note - I have just committed a patch to readelf to make its output 
> slightly more helpful when it encounters problems like this.

I believe there is a readelf bug:

http://sources.redhat.com/bugzilla/show_bug.cgi?id=615

> 
> The 19124 bug is definitely a GCC problem - readelf is just reporting 
> the facts, and as Andrew Pinkski has reported if you compile with 
> -fno-var-tracking the problem goes away.
> 
> >When I used idb, I got
> >
> >(idb) stop in tls_symbolic_operand
> >
> >Info: Optimized variables show as <no value> when no location is
> >allocated.
> >[#1: stop in int tls_symbolic_operand(rtx, enum machine_mode)]
> >(idb) r
> >
> >Is that a gdb/readelf or gcc bug?
> 
> GDB not being able to debug GCC is a GDB problem.  (Or possibly a 
> problem of the compiler than was used to compile the GCC being 
> debugged).  Either way I am pretty sure that readelf is blameless in 
> this situation.

I think gcc may be correct and gdb just can't handle location list
correctly.


H.J.