This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Some make installcheck results 2.6.27.19-170.2.35.fc10.i68/0.9/0.140 commit e1e3ba36
- From: Mark Wielaard <mjw at redhat dot com>
- To: systemtap at sourceware dot org
- Date: Wed, 25 Mar 2009 15:26:57 +0100
- Subject: Some make installcheck results 2.6.27.19-170.2.35.fc10.i68/0.9/0.140 commit e1e3ba36
Some more make installcheck results.
Host: Linux hermans.wildebeest.org 2.6.27.19-170.2.35.fc10.i686 #1 SMP Mon Feb 2
3 13:21:22 EST 2009 i686 i686 i386 GNU/Linux
Snapshot: version 0.9/0.140 commit e1e3ba36
Distro: Fedora release 10 (Cambridge)
# of expected passes 747
# of unexpected failures 19
# of unexpected successes 9
# of expected failures 201
# of unknown successes 2
# of known failures 12
# of untested testcases 4
FAIL: backtrace (1 0)
FAIL: backtrace-unwindsyms (1 0)
These have never worked.
Tracked as PR6961.
FAIL: gtod (224)
Seen this before on i686, not investigated yet.
FAIL: systemtap.base/stmt_rel.stp
"child killed: segmentation violation"
Program received signal SIGSEGV, Segmentation fault.
0x00d6653e in __libdw_find_attr (die=0xbfffc7d0, search_name=82,
codep=0xbfffc780, formp=0xbfffc784) at dwarf_child.c:92
92 + dbg->sectiondata[IDX_debug_abbrev]->d_size);
(gdb) bt
#0 0x00d6653e in __libdw_find_attr (die=0xbfffc7d0, search_name=82,
codep=0xbfffc780, formp=0xbfffc784) at dwarf_child.c:92
#1 0x00d65f86 in dwarf_attr (die=0xbfffc7d0, search_name=82,
result=0xbfffc780) at dwarf_attr.c:69
#2 0x00d66d16 in dwarf_entrypc (die=0xbfffc7d0, return_addr=0xbfffc808)
at dwarf_entrypc.c:65
#3 0x08114986 in dwflpp::iterate_over_srcfile_lines (this=warning: (Internal error: pc 0x8114590 in read in psymtab, but not in symtab.)
pc 0x8114985 in read in psymtab, but not in symtab.) 0x88f5038,
srcfile=0x93c15c4 "fs/bio.c", lines=0xbfffce04, need_single_match=true,
line_type=RELATIVE, callback=0x80fa1e0 <query_srcfile_line>,
data=0xbfffcd34) at tapsets.cxx:1243
#4 0x080f9aff in query_cu (cudie=0xbfffc9c8, arg=0xbfffcd34)
at tapsets.cxx:4074
#5 0x080f9f29 in dwflpp::iterate_over_cus () at tapsets.cxx:1091
elfutils bug?
FAIL: systemtap.base/uprobes_lib.stp
Double calling of uprobe probes. New test.
Tracked as PR9940
FAIL: vars
FAIL: vars parms/locals
vars=child killed: segmentation violation
child process exited abnormally=
rest=child killed: segmentation violation
child process exited abnormally child killed: segmentation violation
child process exited abnormally=
Seems similar to above stmt_rel, tries to probe kernel.statement("bio_copy_user@fs/bio.c+1")
FAIL: warnings (0)
$ /usr/local/systemtap/bin/stap -p4 /tmp/systemtap/testsuite/systemtap.base/warnings.stp
Segmentation fault
Program received signal SIGSEGV, Segmentation fault.
0x00d6653e in __libdw_find_attr (die=0xbfffbf80, search_name=82,
codep=0xbfffbf30, formp=0xbfffbf34) at dwarf_child.c:92
92 + dbg->sectiondata[IDX_debug_abbrev]->d_size);
Seems again similar to vars and stmt_rel.
FAIL: backtrace of yyy_func2 (2)
FAIL: print_stack of yyy_func2 (2)
FAIL: backtrace of yyy_func3 (2)
FAIL: print_stack of yyy_func3 (2)
FAIL: backtrace of yyy_func4 (2)
FAIL: print_stack of yyy_func4 (2)
Needs investigation, but has failed on i686 for a long time.
FAIL: buildok/seventeen.stp
FAIL: buildok/seventeen.stp with server
"integer constant is too large"
Tracked as PR10000
FAIL: systemtap.stress/current.stp startup (timeout)
This seemed to be a real timeout, slow machine, running again with less
load made it complete and PASS.
FAIL: 32-bit access
access FAILED. output of "stap -c /tmp/systemtap/testsuite/staptestpXgxb/access
/tmp/systemtap/testsuite/systemtap.syscall/sys.stp" was:
------------------------------------------
stapio: exit (10) =
I am not sure what is going on here. Running this test by hand makes it PASS.
FAIL: 32-bit net1
Known bug, we are missing accept syscalls on 2.6.27+ kernels.
Tracked as PR6991