From: Hien Nguyen <hien@us.ibm.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: nightly test in ppc64
Date: Tue, 27 Jun 2006 10:05:00 -0000 [thread overview]
Message-ID: <44A078CB.40507@us.ibm.com> (raw)
Nightly test summary
FAIL: ./systemtap.base/kmodule.stp compilation
FAIL: probefunc:kernel.statement(0xc000000000058228) shutdown (eof)
FAIL: ./systemtap.samples/tcptest.stp startup (eof)
FAIL: ./systemtap.stress/current.stp compilation
Running ./systemtap.syscall/test.exp ...
FAIL: acct - I fixed this problem, will check in the fix (ppc64/syscall.stp)
FAIL: chmod - see Note #1 below.
FAIL: dir - see Note #1 below.
FAIL: mmap - see Note #1 below.
FAIL: mount - test case looks for sys_mount where ppc64 use
compat_sys_mount. will check in fix (ppc64/syscall.stp)
FAIL: openclose - see Note #1 below.
FAIL: readwrite - test case
FAIL: signal - Fixed (ppc64/syscall.stp)
FAIL: stat -
FAIL: statfs
FAIL: uid
FAIL: umask - Fixed (ppc64/syscall.stp)
FAIL: unlink - Fixed (ppc64/syscall.stp)
Notes:
1) On ppc64, the test cases actually exercise sys32_open. I added the
another alias to sys32_open but I run into the user_string($filename)
failure. It seems to get a bad address, I am not sure why.
stap -e'probe syscall.sys32_open{log(argstr)}' -c ./openclose
"/etc/ld.so.cache", O_RDONLY
"/lib/libtermcap.so.2", O_RDONLY
"/lib/libdl.so.2", O_RDONLY
"/lib/tls/libc.so.6", O_RDONLY
ERROR: user string copy fault at 0x00000000100 near identifier
'$filename' at
/root/stap_testing_200606261509/src/tapset/ppc64/syscalls.stp:991:25
WARNING: Number of errors: 1, skipped probes: 1
print the user addresses for the same test show that
"[0xffe5e00]", O_RDONLY
"[0xf7fe8c9d]", O_RDONLY
"[0xf7ff85e7]", O_RDONLY
"[0xf7ff9994]", O_RDONLY
"[0x1009730c]", O_RDWR|O_LARGEFILE|O_NONBLOCK <------- error here
"[0xff8cad8]", O_RDONLY
"[0xffffbf80]", O_RDONLY
2) After adding a few more probe aliases to the system call tapset, I
encounter these compilation error when doing this "probe syscall.*{}"
[....]
{standard input}:940330: Error: operand out of range (0x0000000000008fa8
is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:940423: Error: operand out of range (0x0000000000008fb0
is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:940584: Error: operand out of range (0x0000000000008fb8
is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:940595: Error: operand out of range (0x0000000000008fc0
is not between 0xffffffffffff8000 and 0x0000000000007fff)
if I remove them some of the probe aliases then, it compiled. Li
GuangLei, I wonder that you see the samething.
reply other threads:[~2006-06-27 0:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44A078CB.40507@us.ibm.com \
--to=hien@us.ibm.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).