On Wed, Nov 21, 2007 at 12:46:53AM +0200, Arto Huusko wrote:
> 
> It has to do with some JVM feature called safepointing, which is
> implemented by a thread manipulating protection of one page,
> and then yielding until other threads notice the situation
> by getting SIGSEGV, and doing whatever they need to do.
> 
> On NetBSD, the thread getting SIGSEGV doesn't notice that the
> signal was received due to safepointing (and apparently ends up
> restarting the instruction over and over again), because

Hmmm.... that sounds as portable as the bourne shell malloc code...

	David

-- 
David Laight: david@l8s.co.uk