|
From: Eyal L. <ey...@ey...> - 2005-01-23 00:53:39
|
Jeremy Fitzhardinge wrote: > When it is in this state, before you killall -9 valgrind, please run > none/tests/faultstatus (natively, not under Valgrind). If this fails, > it is definitely a kernel bug. > > J Done this, and faultstatus is not failing 'in that state': root@e7:/data2/valgrind/valgrind/none/tests# ./faultstatus Test 0: PASS 1 Test 1: PASS 2 Test 2: PASS 3 Test 3: PASS 4 Test 4: PASS 5 However, running as non-root it does fail 'in that state': eyal@e7:~$ /data2/valgrind/valgrind/none/tests/faultstatus Test 0: FAIL: expected si_code==1, not 0 Test 1: FAIL: expected si_code==2, not 0 Test 2: FAIL: expected si_code==2, not 0 Test 3: FAIL: expected si_code==2, not 0 Test 4: FAIL: expected si_code==1, not 0 My application runs non-root. 'killall' makes it work instantly. This is on vanilla 2.6.11-rc2. Was this reported to linux-kernel? Who is handling it there? I am ready to do testing/investigation as I can reproduce it consistently. I cannot report it myself as I do not know enough about the nature of the problem (or what faultstatus does). However, if this test program is a simple one that should always work but sometimes does not (and can be built stand-alone) then it may be enough for a report. -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> attach .zip as .dat |