|
From: Eyal L. <ey...@ey...> - 2005-01-20 08:21:19
|
Jeremy Fitzhardinge wrote: [trimmed] > I'll note that both FC2 and SUSE 9.2 2.6 kernels seem to show sporadic > problems with delivering signals without proper siginfo information. > That will cause your program to spontaneously SIGSEGV when it tries to > grow the stack, which almost every program will need to do. The kernel > will stay in this state for some indeterminate amount of time, but then > will spontaneously start working again. > > J In case it is the same thing, let me describe how I tested it just now. I have a small test zz35.sh (attached) that simple creates an uninited error, and which I use to see that I get a proper backtrace. I now use it to investigate a different problem where my regression testsuit hangs after a number of successful runs and will not proceed until I shutdown all my servers (thud stopping all valgrind instances). - run my tests. It should do 11-12 of them before failing - wait for my tests to hang - run my zz35 which fails sig 11 (zz35-sig11.log). It fails consistently for as long as I want. - 'killall -9 valgrind' to release my failed tests/servers - without any waiting run my zz35 which works OK again (zz35-ok.log) So, stopping the running valgrind instances allowed zz35 to run OK. There does not seem to be a period where the kernel is in 'a mood', but rather one needs to ensure all valgrind instances are stopped. Which suggests that some sort of global resource (internal to vg) is associated with the failure. Naturally, it could still be a kernel bug that does this. This is with vanilla 2.6.10-ac9. -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> If attaching .zip rename to .dat |