This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug testsuite/5770] Seen lot of "eof" errors on systemtap-20080216 snapshot
- From: "mhiramat at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 19 Feb 2008 17:04:36 -0000
- Subject: [Bug testsuite/5770] Seen lot of "eof" errors on systemtap-20080216 snapshot
- References: <20080219085344.5770.srinivasa@in.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mhiramat at redhat dot com 2008-02-19 17:04 -------
(In reply to comment #0)
> Environment: Kernel-2.6.25-rc2, Elfutils-0.131 systemtap-20080216.
>
> I saw lot of "systemtap eof" errors while executing weekly tests.
I also had a same case on 2.6.24-mm1.
[snip]
> But systemtap.log doesn't show any error message.
> ====================================================
> Running
> /home/systemtap/tmp/stap_testing_200802190556/src/testsuite/systemtap.base/if.exp
> ...
> Pass 1: parsed user script and 38 library script(s) in 960usr/10sys/1061real ms.^M
> Pass 2: analyzed script: 2 probe(s), 0 function(s), 0 embed(s), 0 global(s) in
> 10usr/0sys/15real ms.^M
> Pass 3: translated to C into
> "/tmp/stapT7Jn5K/stap_4aaa9f77a8d1234ddacea99b8c1a212f_467.c" in 0usr/0sys/2real
> ms.^M
> Pass 4: compiled C into "stap_4aaa9f77a8d1234ddacea99b8c1a212f_467.ko" in
> 3620usr/370sys/4385real ms.^M
> Pass 5: starting run.^M
> systemtap starting probe^M
> PASS: systemtap.base/if.stp startup
> PASS: systemtap.base/if.stp load generation
> ^Csystemtap ending probe^M
Here, I found a break-code(^C) which tcl code sent (as a signal) to stap.
On 2.5.24, NO ^C appeared in the output. Thus the test does not expect it.
I think that is why the test failed to catch the test result.
I'm not sure this (kernel's?) behavior is correct. It is possible that is
a regression of the kernel.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5770
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.