[Python-bugs-list] Signal processing bug (Linux threads, readline, whatever else) (PR#196)

[flight@mathi.uni-heidelberg.de]

--dDRMvlgZJXvWKvBx
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Ok, one more data point:

On Fri, Feb 11, 2000 at 08:29:43AM -0500, Randall Hopper wrote:
> You know, I think you may have it.  On IRIX, I don't have Python built
> with threads.  However, on FreeBSD at home I'd guess that it is (I built =
it
> from ports).  My IRIX python has no problem with Ctrl-C while my FreeBSD
> version at home locks up with Ctrl-C.  I rebuilt my IRIX Python
> --with-thread, and now it hangs when Ctrl-C is hit.

And now, we're three: When using threads and readline, Ctrl-C hangs IRIX and
FreeBSD and kills Linux Python.

This doesn't sound like a kernel problem, more like a problem with readline
not being thread-safe I guess.

    Gregor
   =20

--dDRMvlgZJXvWKvBx
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4pBQq3eVfDf25G40RAUbSAJ41b+DgwHEmRUm0uQcJLjvZ3ROiSwCdH8Xq
jFH5J1TsLQBbQTPU5Xvv0Bo=
=0j16
-----END PGP SIGNATURE-----

--dDRMvlgZJXvWKvBx--