Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 16 Jul 2001 12:17:26 -0400 From: Jason Tishler To: Greg Smith Cc: gsmith AT nc DOT rr DOT com, Cygwin-Developers Subject: Re: Threaded Cygwin Python Import Problem Message-ID: <20010716121726.E614@dothill.com> Mail-Followup-To: Greg Smith , gsmith AT nc DOT rr DOT com, Cygwin-Developers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B530F25.ECF8846E@trex.rtpnc.epa.gov> User-Agent: Mutt/1.3.18i Organization: Dot Hill Systems Corp. Greg, On Mon, Jul 16, 2001 at 11:58:29AM -0400, Greg Smith wrote: > Hi Jason, I believe I have recreated the problem on a nt4 sp6 pIII-650 > system, but I just want to make sure: > > GSmith AT GREG /Python-2.1 > $ ./python /tmp/test.py > child execvp-ing > > and the script never finishes, correct ? Yes! (I'm relieved that it was not just me!) If you kill the child, then you should see the following: $ ./python ../nothreads/test.py child execvp-ing status = 15 parent done Instead if you attach to the child, then you should see a stack trace like the one in the following: http://www.cygwin.com/ml/cygwin-developers/2001-07/msg00074.html Thanks, Jason -- Jason Tishler Director, Software Engineering Phone: 732.264.8770 x235 Dot Hill Systems Corp. Fax: 732.264.8798 82 Bethany Road, Suite 7 Email: Jason DOT Tishler AT dothill DOT com Hazlet, NJ 07730 USA WWW: http://www.dothill.com