From: Mark Wielaard <mjw@redhat.com>
To: Zheng Da <zhengda1936@gmail.com>
Cc: Josh Stone <jistone@redhat.com>, agentzh <agentzh@gmail.com>,
"systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: Re: [BUG] syscall.unlink no longer works after upgrading kernel to 3.7.3
Date: Tue, 28 May 2013 19:15:00 -0000 [thread overview]
Message-ID: <20130528191449.GA31042@toonder.wildebeest.org> (raw)
In-Reply-To: <CAFLer83DQhCQg7Y3NKR0EUYePzp+fETDTeYEthUXKarAySM0_g@mail.gmail.com>
On Tue, May 28, 2013 at 02:52:48PM -0400, Zheng Da wrote:
> I think I got a very similar error in Ubuntu:
> semantic error: not accessible at this address [man error::dwarf]
> (0xffffffff81480e80, dieoffset: 0x43d730b): identifier '$sdev' at
> :10:6
> source: if ($sdev->host->host_no == 9 && $sdev->id == 1) {
> ^
> I use Linux v3.8.12, and gcc version is 4.6.3.
> Is there any better fix for this problem? I checked the workaround for
> perf, but I don't know how to apply it to systemtap.
I believe the patch/commit you are looking for is:
commit 45b02a36c31d857a0a7d17fc86e1b4e9d15df680
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Tue Feb 12 21:32:30 2013 -0500
PR15123: work around broken gcc debuginfo for -mfentry functions
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54793 interferes with the
calm zen-like state of probing function parameters in programs built
with CFLAGS=-mfentry, due to a dwarf location-list problem. This
patch adds a heuristic function dwflpp::pr15123_retry_addr() that
offers callers a post-mfentry-address alternative for locating
variables. Will they use it, or not? Join us next week, as our
heroes encounter ... angry mr. dwarf, five steps away.
* dwflpp.cxx (pr15123_retry_addr): New function.
(translate_location): Call it, in order to enable $var
and $$parms resolution.
* tapsets.cxx (saveargs): Call it, in order to enable
stap -L <probe> listings.
http://sourceware.org/git/?p=systemtap.git;a=patch;h=45b02a36c31d857a0a7d17fc86e1b4e9d15df680
Cheers,
Mark
next prev parent reply other threads:[~2013-05-28 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 6:35 agentzh
2013-02-05 8:57 ` Mark Wielaard
2013-02-05 17:30 ` Josh Stone
2013-05-28 18:53 ` Zheng Da
2013-05-28 19:15 ` Mark Wielaard [this message]
2013-05-28 19:57 ` Zheng Da
2013-05-28 20:22 ` Josh Stone
2013-05-28 20:32 ` Mark Wielaard
2013-05-28 21:36 ` Zheng Da
2013-05-28 22:51 ` Josh Stone
2013-05-28 23:52 ` Zheng Da
2013-05-29 0:19 ` Josh Stone
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=20130528191449.GA31042@toonder.wildebeest.org \
--to=mjw@redhat.com \
--cc=agentzh@gmail.com \
--cc=jistone@redhat.com \
--cc=systemtap@sourceware.org \
--cc=zhengda1936@gmail.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).