From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10388] New: Support DW_OP_call_frame_cfa
Date: Tue, 14 Jul 2009 09:35:00 -0000 [thread overview]
Message-ID: <20090714093510.10388.mjw@redhat.com> (raw)
Currently there are several failures in sdt.exp and exelib.exp on fedora rawhide
because it has a newer gcc that supports a more compact debuginfo format by
using some dwarf3 features. In particular it now emits DW_OP_call_frame_cfa if
there is eh_frame information available. Systemtap and elfutils don't support
this yet. The failures look like:
Got "semantic error: dwarf_getlocation_addr (form 0xa): invalid DWARF
The dwarf isn't invalid, elfutils dwarf_get_location() just didn't recognize
DW_OP_call_frame_cfa (this has been fixed in elfutils git, not released yet),
and loc2c also doesn't handle DW_OP_call_frame_cfa. Adding support will rely on
the new elfutils cfi support (only available in git atm).
See also https://fedorahosted.org/pipermail/elfutils-devel/2009-July/000457.html
--
Summary: Support DW_OP_call_frame_cfa
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mjw at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10388
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-07-14 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 9:35 mjw at redhat dot com [this message]
2009-07-14 9:35 ` [Bug translator/10388] " mjw at redhat 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=20090714093510.10388.mjw@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).