| Server IP : 118.27.122.248 / Your IP : 216.73.216.124 Web Server : Apache System : Linux web0264.sh.tyo1 4.18.0-553.79.1.lve.el7h.x86_64 #1 SMP Wed Oct 15 16:34:46 UTC 2025 x86_64 User : c9415830 ( 11735) PHP Version : 8.4.17 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /opt/alt/python27/lib64/python2.7/test/ |
Upload File : |
� �q2_c @ 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( ( s3 /opt/alt/python27/lib64/python2.7/test/fork_wait.pyt setUp s c C sH d | _ x | j D] } | j � q Wd } | j 2t j | j � d S( Ni ( R R t joint NoneR t threading_cleanupR ( R t thread( ( s3 /opt/alt/python27/lib64/python2.7/test/fork_wait.pyt tearDown s c C sL xE | j sG t j � | j | <y t j t � Wq t k rC q Xq Wd S( N( R t ost getpidR t timet sleept SHORTSLEEPt IOError( R t id( ( s3 /opt/alt/python27/lib64/python2.7/test/fork_wait.pyt f) s c C s� xP t d � D]B } t j | t j � \ } } | | k r>