|
From: Jeremy F. <je...@go...> - 2005-01-25 18:24:59
|
On Mon, 2005-01-24 at 21:35 +1100, Eyal Lebedinsky wrote: > 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. Well, I did fix a real bug, but there could be another one. Lots of bugs have "died with SIGSEGV" as their symptom. Could you file a bug for this? And if you can give me some way to reproduce this, that would be helpful. There are only a few places within Valgrind where it would quietly die with SIGSEGV without being able to say anything. I'm not sure what it might be in this case. J |