This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
some test results
- From: Mark Wielaard <mjw at redhat dot com>
- To: systemtap at sourceware dot org
- Date: Tue, 24 May 2011 13:08:04 +0200
- Subject: some test results
Hi,
I recently ran the systemtap installcheck testsuite, but dejazilla
doesn't seem to accept systemtap.sum files anymore. So I thought I post
my test results here, to see if people know about the failures already:
Host: Linux springer.wildebeest.org 2.6.35.13-91.fc14.x86_64 #1 SMP Mon May 23 16:15:48 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux
Snapshot: version 1.5/0.152 commit release-1.5-2-gbd7f76a
GCC: 4.5.1 [gcc (GCC) 4.5.1 20100924 (Red Hat 4.5.1-4)]
Distro: Fedora release 14 (Laughlin)
=== systemtap Summary ===
# of expected passes 1785
# of unexpected failures 31
# of unexpected successes 8
# of expected failures 243
# of known failures 3
# of untested testcases 64
# of unsupported tests 2
FAIL: rep_ret-m64 (2, 1, 0)
FAIL: rep_ret-m32 (2, 1, 0)
These are now allowed (because they make sense in some AMD optimization
case?), so other failing instructions should be found.
FAIL: sdt_misc (2) shared V2_kprobe
FAIL: sdt_misc (0) V2_kprobe shared attach
FAIL: sdt_misc (2) shared V2_uprobe
FAIL: sdt_misc (0) V2_uprobe shared attach
The systemtap.log file doesn't immediately give a clue.
FAIL: vta-test-m64
FAIL: vta-test-m32
Got "semantic error: failed to retrieve location attribute for local
'a' (dieoffset: 0xfb): identifier '$a'
at /home/mark/src/systemtap/testsuite/systemtap.base/vta-test.stp:2:27"
Needs some investigation, I assume this is related to the GCC version
used.
FAIL: warnings (0)
semantic error: multiple addresses for fs/bio.c:256 (try fs/bio.c:254 or fs/bio.c:257)
semantic error: no match while resolving probe point kernel.statement("bio_init@fs/bio.c+1")
semantic error: no match while resolving probe point probea
Pass 2: analysis failed. Try again with another '--vp 01' option.
So seems related to the kernel version used. Might not be a good probe
point to try?
FAIL: systemtap.examples/general/badname build
FAIL: systemtap.examples/general/badname run
attempting command stap -g -p4 badname.stp
OUT semantic error: unable to find local 'child' near pc 0xffffffff811217bd in may_create fs/namei.c ( (alternatives: $dir): identifier '$child' at badname.stp:16:7
source: if ($child->d_inode || $dir->i_flags & 16) next
^
semantic error: unable to find local 'child' near pc 0xffffffff811217bd in may_create fs/namei.c ( (alternatives: $dir): identifier '$child' at :19:28
source: if (filter(kernel_string($child->d_name->name)))
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
child process exited abnormally
RC 1
Bad script/probe point vs kernel used?
FAIL: systemtap.examples/io/iostat-scsi run
attempting command stap -g iostat-scsi.stp 1 -c "sleep 0.2"
OUT ERROR: kernel string copy fault at 0x000000000000000c near identifier 'kernel_string' at /usr/local/install/systemtap/share/systemtap/tapset/conversions.stp:18:10
WARNING: Number of errors: 1, skipped probes: 1
Pass 5: run failed. Try again with another '--vp 00001' option.
child process exited abnormally
RC 1
FAIL: systemtap.examples/io/iostat-scsi run
This PASSes when run by hand?
FAIL: mark-uprobesgcc-O3default-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug (3)
FAIL: mark-uprobesgcc-O3default-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug (3)
FAIL: mark-uprobesgcc-O3default-pie-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug (3)
FAIL: mark-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug (3)
The func_count probe point is missed in these cases, don't know why.
Everything else seems to work for these testcases.
FAIL: semok/thirtynine.stp
spawn stap -p2 /home/mark/src/systemtap/testsuite/semok/thirtynine.stp
semantic error: not accessible at this address (0xffffffff81469068, dieoffset: 0x624965): identifier '$prev' at /home/mark/src/systemtap/testsuite/semok/thirtynine.stp:6:40
source: printf("switch from=0x%x to=0x%x\n", $prev, $next)
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
semantic error: not accessible at this address (0xffffffff81469068, dieoffset: 0x624965): identifier '$prev' at /home/mark/src/systemtap/testsuite/semok/thirtynine.stp:6:40
source: printf("switch from=0x%x to=0x%x\n", $prev, $next)
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
wait results: 17640 exp15 0 1
FAIL: RING_BUFFER startup (eof)
In file included from /usr/local/install/systemtap/share/systemtap/runtime/transport/transport.c:56:0,
from /usr/local/install/systemtap/share/systemtap/runtime/print.c:18,
from /usr/local/install/systemtap/share/systemtap/runtime/runtime.h:128,
from /tmp/stapajX0yB/stap_b2cc96b28fc54216f7296bd1b9106bb7_935.c:59:
/usr/local/install/systemtap/share/systemtap/runtime/transport/ring_buffer.c: In function â_stp_ring_buffer_consumeâ:
/usr/local/install/systemtap/share/systemtap/runtime/transport/ring_buffer.c:255:2: error: too few arguments to function âring_buffer_consumeâ
include/linux/ring_buffer.h:126:1: note: declared here
/usr/local/install/systemtap/share/systemtap/runtime/transport/ring_buffer.c: In function â_stp_peek_next_eventâ:
/usr/local/install/systemtap/share/systemtap/runtime/transport/ring_buffer.c:291:3: error: too few arguments to function âring_buffer_peekâ
include/linux/ring_buffer.h:123:1: note: declared here
cc1: warnings being treated as errors
/usr/local/install/systemtap/share/systemtap/runtime/transport/ring_buffer.c: In function â_stp_buffer_iter_startâ:
/usr/local/install/systemtap/share/systemtap/runtime/transport/ring_buffer.c:398:7: error: passing argument 1 of âring_buffer_read_startâ from incompatible pointer type
include/linux/ring_buffer.h:132:6: note: expected âstruct ring_buffer_iter *â but argument is of type âstruct ring_buffer *â
/usr/local/install/systemtap/share/systemtap/runtime/transport/ring_buffer.c:398:7: error: too many arguments to function âring_buffer_read_startâ
include/linux/ring_buffer.h:132:6: note: declared here
/usr/local/install/systemtap/share/systemtap/runtime/transport/ring_buffer.c:398:7: error: void value not ignored as it ought to be
make[4]: *** [/tmp/stapajX0yB/stap_b2cc96b28fc54216f7296bd1b9106bb7_935.o] Error 1
make[3]: *** [_module_/tmp/stapajX0yB] Error 2
Pass 4: compiled C into "stap_b2cc96b28fc54216f7296bd1b9106bb7_935.ko" in 340usr/260sys/631real ms.
Pass 4: compilation failed. Try again with another '--vp 0001' option.
FAIL: 64-bit dup nd_syscall
FAIL: 64-bit eventfd nd_syscall
FAIL: 64-bit inotify nd_syscall
FAIL: 64-bit pipe nd_syscall
FAIL: 64-bit poll nd_syscall
FAIL: 64-bit signalfd nd_syscall
FAIL: 32-bit dup nd_syscall
FAIL: 32-bit eventfd nd_syscall
FAIL: 32-bit inotify nd_syscall
FAIL: 32-bit net1 nd_syscall
FAIL: 32-bit pipe nd_syscall
FAIL: 32-bit poll nd_syscall
FAIL: 32-bit signalfd nd_syscall
I think all of the above are known failures.
Cheers,
Mark