|
From: Eyal L. <ey...@ey...> - 2005-01-23 06:09:02
|
Jeremy Fitzhardinge wrote: > On Sun, 2005-01-23 at 11:53 +1100, Eyal Lebedinsky wrote: > >>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. > > > Hm, I've worked out what it is, and it probably is a Valgrind bug. > There's a system-wide limit to the number of queued signals; if that > limit gets hit, then signals are delivered without extra info. I can > reproduce it easily if I change faultstatus to send itself a lot of > blocked signals before doing the main part of the test. > > Does your test do a lot of thread exits? Probably. My testsuit is running clients against servers and each client session gets a thread, and a typical test will have no more than 10 threads at a time active on the server. I have seen the failure after 11 tests or it managed up to 25. > J > -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> attach .zip as .dat |