public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/16215] SPARC: can't compute CFA for this frame
Date: Wed, 27 Nov 2013 16:10:00 -0000 [thread overview]
Message-ID: <bug-16215-4717-AvAi3lInee@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16215-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16215
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
--- Comment #2 from Tom Tromey <tromey at redhat dot com> ---
I looked at the ELF with readelf a bit but nothing
stood out as obviously wrong.
I think it would be worthwhile to track down where
gdb is misinterpreting the data. That gcc patch
definitely should not be needed; and I would have
thought gdb 7.6 would have all the needed DWARF 4 updates.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-27 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 8:10 [Bug backtrace/16215] New: " sebastian.huber@embedded-brains.de
2013-11-27 13:09 ` [Bug backtrace/16215] " sebastian.huber@embedded-brains.de
2013-11-27 16:10 ` tromey at redhat dot com [this message]
2013-11-28 0:25 ` mkhoory at eiast dot ae
2014-03-24 18:21 ` sebastian.huber@embedded-brains.de
2014-09-24 11:39 ` sebastian.huber@embedded-brains.de
2014-12-13 13:27 ` cvs-commit at gcc dot gnu.org
2014-12-13 15:26 ` cvs-commit at gcc dot gnu.org
2014-12-25 0:46 ` cvs-commit at gcc dot gnu.org
2014-12-31 7:22 ` cvs-commit at gcc dot gnu.org
2015-01-15 11:40 ` brobecker at gnat dot com
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=bug-16215-4717-AvAi3lInee@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).