From: Nick Clifton <nickc@redhat.com>
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?
Date: Wed, 22 Dec 2004 11:09:00 -0000 [thread overview]
Message-ID: <41C9577D.3010509@redhat.com> (raw)
In-Reply-To: <20041222011627.GA15293@lucon.org>
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
next prev parent reply other threads:[~2004-12-22 11:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 1:16 H. J. Lu
2004-12-22 11:09 ` Nick Clifton [this message]
2004-12-22 18:25 ` H. J. Lu
2004-12-23 3:43 ` Daniel Jacobowitz
2004-12-30 19:24 ` GDB 6.3 assumes that DW_AT_frame_base exists H. J. Lu
2004-12-30 19:36 ` H. J. Lu
2004-12-30 19:56 ` H. J. Lu
2004-12-30 20:07 ` Daniel Jacobowitz
2004-12-30 20:23 ` Gdb generates location list without DW_AT_frame_base H. J. Lu
2004-12-30 20:28 ` Daniel Jacobowitz
2004-12-30 20:52 ` Gdb generates DW_OP_fbreg in " H. J. Lu
2004-12-30 20:56 ` Gdb generates " Daniel Berlin
2004-12-30 21:05 ` H. J. Lu
2004-12-31 0:35 ` Daniel Berlin
2004-12-31 19:57 ` H. J. Lu
2004-12-31 20:09 ` Daniel Berlin
2004-12-31 20:11 ` H. J. Lu
2004-12-31 20:16 ` Daniel Berlin
[not found] ` <20041231163806.GA1335@lucon.org>
[not found] ` <Pine.LNX.4.60.0412311158280.27590@dberlin.org>
[not found] ` <20041231184405.GA2182@lucon.org>
[not found] ` <Pine.LNX.4.60.0412311451060.6844@dberlin.org>
[not found] ` <Pine.LNX.4.60.0412311509360.6844@dberlin.org>
[not found] ` <20041231215010.GA5722@lucon.org>
[not found] ` <20041231215443.GA5853@lucon.org>
[not found] ` <Pine.LNX.4.60.0412311656360.6844@dberlin.org>
[not found] ` <20041231220324.GA5987@lucon.org>
2005-01-01 19:15 ` gcc 4.0 " H. J. Lu
2005-01-01 20:09 ` Daniel Jacobowitz
2005-01-01 20:50 ` Daniel Berlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41C9577D.3010509@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox