Przemys?aw Pawe?czyk wrote:

> Matthias Scheler answered:

> > S That's a bug in the application.
> 
> One of my Polish co-workers said just contrary - it has to be NetBSD
> error as it is threads' synchronization problem.

I encountered such a problem two times so far. Both were real problems in
the application where Linux did not care about it.

  "It doesn't happen on Linux, so it must be NetBSD's bug"
is not a valid statement, the same as
   "NetBSD's threads are free of bugs, it must be the application's fault"
is invalid. It is my impression that people have encountered more
such situations where the application was at fault.

ciao
     Klaus