Your IP : 216.73.216.103
�
zfc @ s� d Z d d l Z d d l Z d d l Z d d l Z d d l j Z e j d � Z d Z d Z
d Z d e j f d � � YZ
d S( s� This test case provides support for checking forking and wait behavior.
To test different wait behavior, override the wait_impl method.
We want fork1() semantics -- only the forking thread survives in the
child after a fork().
On some systems (e.g. Solaris without posix threads) we find that all
active threads survive in the child after a fork(); this is an error.
While BeOS doesn't officially support fork and native threading in
the same application, the present example should work just fine. DC
i����Nt threadingi g �?i t ForkWaitc B s5 e Z d � Z d � Z d � Z d � Z d � Z RS( c C s. t j � | _ i | _ d | _ g | _ d S( Ni ( t supportt threading_setupt _threading_keyt alivet stopt threads( t self( ( s&