From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-20384-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 9426 invoked by alias); 22 Dec 2004 11:09:51 -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 9194 invoked from network); 22 Dec 2004 11:09:35 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sourceware.org with SMTP; 22 Dec 2004 11:09:35 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iBMB9U7j011044;
	Wed, 22 Dec 2004 06:09:35 -0500
Received: from pobox.surrey.redhat.com (pobox.surrey.redhat.com [172.16.10.17])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iBMB9Tr28307;
	Wed, 22 Dec 2004 06:09:29 -0500
Received: from [172.31.0.98] (vpnuser4.surrey.redhat.com [172.16.9.4])
	by pobox.surrey.redhat.com (8.12.8/8.12.8) with ESMTP id iBMB9Sge015907;
	Wed, 22 Dec 2004 11:09:28 GMT
Message-ID: <41C9577D.3010509@redhat.com>
Date: Wed, 22 Dec 2004 11:09:00 -0000
From: Nick Clifton <nickc@redhat.com>
User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041201)
MIME-Version: 1.0
To: "H. J. Lu" <hjl@lucon.org>
CC: gcc@gcc.gnu.org, GDB <gdb@sources.redhat.com>, binutils@sources.redhat.com
Subject: Re: Is this a gcc, gdb or readelf bug?
References: <20041222011627.GA15293@lucon.org>
In-Reply-To: <20041222011627.GA15293@lucon.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-12/txt/msg00109.txt.bz2

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.

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.

Cheers
   Nick