From: David Smith <dsmith@redhat.com>
To: Vincent Bernat <bernat@luffy.cx>
Cc: systemtap@sourceware.org
Subject: Re: semantic error: not accessible at this address
Date: Fri, 27 Sep 2013 21:19:00 -0000 [thread overview]
Message-ID: <5245EAE2.1060500@redhat.com> (raw)
In-Reply-To: <87ioxmf2e9.fsf@guybrush.luffy.cx>
On 09/27/2013 03:14 PM, Vincent Bernat wrote:
> Hi!
>
> I have the following error when trying to use iotop example with a 3.11
> kernel:
>
> semantic error: not accessible at this address [man error::dwarf] (0xffffffff811b42b0, dieoffset: 0x177422e): identifier '$file' at /usr/share/systemtap/tapset/linux/vfs.stp:855:9
> source: file = $file
> ^
>
> Pass 2: analysis failed. [man error::pass2]
>
> I have read the wiki but if I use eu-readelf on vmlinux, I get the
> appropriate stuff:
>
> [1774208] subprogram
> external (flag) Yes
> name (strp) "vfs_write"
> decl_file (data1) 1
> decl_line (data2) 459
> prototyped (flag) Yes
> type (ref4) [17643bb]
> low_pc (addr) 0xffffffff811b42b0
> high_pc (addr) 0xffffffff811b44a9
> frame_base (data4) location list [5ec58b]
> sibling (ref4) [17744b9]
> [177422e] formal_parameter
> name (strp) "file"
> decl_file (data1) 1
> decl_line (data2) 459
> type (ref4) [1769ace]
> location (data4) location list [5ec5ff]
>
> The kernel was compiled with gcc 4.6.3 (the one in Ubuntu Precise). I
> have tried with gcc 4.7.3 instead but I get less complete information
> (the formal parameter lose its name).
>
> systemtap seems to use the right debug file:
>
> focused on module 'kernel' = [0xffffffff81000000-0xffffffff8240e000, bias 0
> file /usr/lib/debug/boot/vmlinux-3.11.0-7-generic ELF machine |x86_64 (code
> 62)
>
> How could I fix this?
This could certainly be a systemtap problem. To help narrow this down a
bit, could you show us the output of the following 2 commands?
# stap -V
# stap -L 'kernel.function("vfs_write").*'
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
next prev parent reply other threads:[~2013-09-27 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 20:14 Vincent Bernat
2013-09-27 21:19 ` David Smith [this message]
2013-09-27 21:27 ` Vincent Bernat
[not found] ` <y0mvc1mt0k7.fsf@fche.csb>
[not found] ` <8738opg9ym.fsf@guybrush.luffy.cx>
2013-09-27 23:04 ` Frank Ch. Eigler
2013-09-27 23:20 ` Vincent Bernat
2013-09-27 23:25 ` Frank Ch. Eigler
2013-09-27 23:49 ` Vincent Bernat
2013-09-28 0:02 ` Frank Ch. Eigler
2013-09-28 7:48 ` Vincent Bernat
2013-09-28 12:46 ` Frank Ch. Eigler
2013-09-28 16:50 ` [PATCH] PR15123: when PR15123_ASSUME_MFENTRY is set, don't check for -mfentry flag Vincent Bernat
2013-09-28 16:55 ` semantic error: not accessible at this address Vincent Bernat
2013-09-29 14:12 ` Frank Ch. Eigler
2013-09-30 7:05 ` Vincent Bernat
2013-09-30 8:12 ` Vincent Bernat
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=5245EAE2.1060500@redhat.com \
--to=dsmith@redhat.com \
--cc=bernat@luffy.cx \
--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).