|
From: Eyal L. <ey...@ey...> - 2005-01-24 10:35:37
|
Jeremy Fitzhardinge wrote: > On Thu, 2005-01-20 at 13:06 +1100, Eyal Lebedinsky wrote: > >>I would like to offer another observation. I just created a simple program >>in an attempt to demonstrate the laconic report problem. Instead, it crashed >>(sig 11) on a return. > > OK, I just checked in a fix for this too. > > J It still crashes, but differently. faultstatus does not fail anymore, but my tests still fail. The pattern is that one program fails with /ssa/builds/20050118g-vgi/bin/showtime: line 81: 10967 Segmentation fault $valgrind_prefix --logfile-fd=9 $orig "$@" 9>>$log The log does not show any errors. Actually, this last run of showtime has not a single line from VG in the log, as if vg itself died quietly. And after this I cannot run anything. This is due to the segfault happening when the failed program was holding a semaphore. This is most unusual because that sem is held for a very brief time, and I do not expect a random crash to happen just then. The fact is that these crashes are very common, actually the earlier problem (the sig11 now patched) was causing exactly the same thing, and I always had to manually remove the sem. Almost as if the fix is not just right. In short, I still have a problem, and it happens about the same time into my tests as the sig11 did. -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> attach .zip as .dat |