|
From: Jeremy F. <je...@go...> - 2005-01-23 01:54:33
|
On Sun, 2005-01-23 at 11:53 +1100, Eyal Lebedinsky wrote: > 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. OK, definitely a kernel problem. faultstatus shouldn't depend on UID at all. > 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 haven't seen it reported against a stock kernel, so I haven't reported it to linux-kernel. > 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. Yes. What does your test suite do? How much can you simplify it and get the same result? J |