From: Steve Dickson <SteveD@redhat.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Strange stap error...
Date: Sat, 19 Dec 2009 17:45:00 -0000 [thread overview]
Message-ID: <4B2D113E.3010309@RedHat.com> (raw)
I'm getting the following error:
$ sudo ~/bin/stap -g inode_permission.stp
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
Copy failed ("/tmp/stapwUrw9k/stap_f69367bbfe0f310d5472acdca1010f45_2000.ko" to "/home/steved/.systemtap/cache/f6/stap_f69367bbfe0f310d5472acdca1010f45_2000.ko"): No such file or directory
ERROR: Unable to canonicalize path "/tmp/stapwUrw9k/stap_f69367bbfe0f310d5472acdca1010f45_2000.ko": No such file or directory
Retrying, after attempted removal of module stap_f69367bbfe0f310d5472acdca1010f45_2000 (rc -1)
ERROR: Unable to canonicalize path "/tmp/stapwUrw9k/stap_f69367bbfe0f310d5472acdca1010f45_2000.ko": No such file or directory
Pass 5: run failed. Try again with another '--vp 00001' option.
Using the following version of stap (straight out of the git tree)
$ ~/bin/stap -V
SystemTap translator/driver (version 1.0/0.143 commit release-1.0-390-g39b375a)
Copyright (C) 2005-2009 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
Using a relativity new kernel...
$ uname -a
Linux redhat 2.6.32-2.nfs41.el6.x86_64.debug #1 SMP Fri Dec 18 08:42:45 EST 2009 x86_64 GNU/Linux
With the following tap script
$ cat inode_permission.stp
probe kernel.function("inode_permission")
{
printf("inode_permission: inode %p mask 0x%x\n", $inode, $mask);
}
probe kernel.function("inode_permission").return
{
printf(" inode_permission: return %d\n", $return);
}
probe begin { log("inode_permission probe") }
probe end { log("inode_permission probe") }
any ideas?
steved.
next reply other threads:[~2009-12-19 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 17:45 Steve Dickson [this message]
2009-12-19 21:41 ` Mark Wielaard
2009-12-20 20:29 ` Frank Ch. Eigler
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=4B2D113E.3010309@RedHat.com \
--to=steved@redhat.com \
--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).