Re: pkg/51657: Python (2.7): interpreter hangs on exit after a call to subproccess.Popen()

[Oskar Skog <oskar.skog.finland%gmail.com@localhost>]

The following reply was made to PR pkg/51657; it has been noted by GNATS.

From: Oskar Skog <oskar.skog.finland%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/51657: Python (2.7): interpreter hangs on exit after a call
 to subproccess.Popen()
Date: Sun, 27 Nov 2016 22:43:55 +0200

 > (a) is this a Python bug? (e.g. does it happen on other OSes?)
 
 It does not happen on any other OSes I have tested on.  Those OSes
 include FreeBSD 9 and 10, OpenBSD 5.8, Minix 3.3, openindiana (illumos
 distribution (OpenSolaris derivate)), Haiku (BeOS clone) and various
 GNU/Linux distributions.
 
 
 > (b) what does ps -l show for the hanging process?
  UID PID PPID   CPU PRI NI  VSZ  RSS WCHAN STAT TTY      TIME COMMAND
 1000 605  612 27555  27  0 9092 4616 -     R    ttyE0 4:27.21 /usr/pkg/bin/pyth
 
 command is /usr/pkg/python ./bug
 
 
 >  (c) if you run the script with ktrace, what are the last few things
 > that appear when you run kdump to show the trace?
 
    670      1 python2.7 GIO   fd 1 wrote 18 bytes
        "Program finished.\n"
    670      1 python2.7 RET   write 18/0x12
    670      1 python2.7 CALL
 __sigaction_sigtramp(SIGINT,0xbfbfec7c,0xbfbfec64,0xbb9ba1a0,2)
    670      1 python2.7 RET   __sigaction_sigtramp 0
    670      1 python2.7 CALL  __wait450(0x297,0xbfbfe588,1,0)
    670      1 python2.7 RET   __wait450 0
    670      1 python2.7 PSIG  SIGINT SIG_DFL: code=SI_NOINFO