From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16596] Support DW_OP_GNU_entry_value in location expressions
Date: Mon, 10 Mar 2014 09:41:00 -0000 [thread overview]
Message-ID: <bug-16596-6586-fAkEUzmyRx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16596-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16596
--- Comment #2 from Mark Wielaard <mjw at redhat dot com> ---
(In reply to David Smith from comment #1)
> Note that I'm seeing DW_OP_GNU_entry_value errors on rawhide x86_64
> (3.14.0-0.rc4.git3.1.fc21.x86_64) with HEAD systemtap:
>
> unhandled DW_OP_GNU_entry_value in DWARF expression [0] at 0 (0xf3: 1, 139892792287890)
Could you try to get a bit more information about this? (We also might want to
extend the error/warning message since it doesn't provide the DIE offset where
this happened.) It would be nice to know exactly at which address stap places
the probe and which location list entry contained the DW_OP_GNU_entry_value.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-03-10 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 23:05 [Bug translator/16596] New: " mjw at redhat dot com
2014-02-19 20:59 ` [Bug translator/16596] " jlebon at redhat dot com
2014-03-05 16:42 ` dsmith at redhat dot com
2014-03-10 9:41 ` mjw at redhat dot com [this message]
2014-03-13 17:14 ` mjw at redhat dot com
2014-03-14 8:50 ` mjw at redhat dot com
2016-05-24 18:17 ` fche at redhat dot com
2017-05-15 19:49 ` jistone at redhat dot com
2017-05-15 19:50 ` jistone at redhat dot com
2017-09-12 17:10 ` dsmith at redhat dot com
2018-11-13 16:08 ` fche 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=bug-16596-6586-fAkEUzmyRx@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).