[Twisted-Python] Weird, apparently platform-dependent bug that hoses reactor

Steve Waterbury golux at comcast.net
Thu Jun 26 23:57:23 EDT 2003

Itamar Shtull-Trauring wrote:
> On Thu, 26 Jun 2003 22:10:06 -0400
> Steve Waterbury <golux at comcast.net> wrote:
>>The platform-dependent aspect is that we have run the
>>exact same code on Debian (unstable) have *not* seen
>>this traceback there.  We get the traceback on a
>>Red Hat 9 (2.4.20-18.9) machine.
> We had one other report, Redhat 7.3.

Aha.  I wonder what version of Python.

> Are you using Redhat Python RPMs? 

Sort of -- not the one that comes with the RH distro, but this
one from python.org:

python-2.2.3-26.src.rpm (Red Hat 9 updated Source RPM, 7007263 bytes)

> Can you reproduce the bug without
> depending on Twisted? If doing signal.signal(...etc..) by itself causes
> this problem, it's obviously not a Twisted problem.

signal.signal by itself seems to be okay:

[waterbug at golux test]$ python
Python 2.2.3 (#1, Jun 25 2003, 22:41:47)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import signal
 >>> signal.signal(signal.SIGINT, signal.SIG_DFL)
<built-in function default_int_handler>

> Are you doing reactor.run() in a thread

Nope, not invoking any threads at all in my code.

Thanks for the suggestions, Itamar.


More information about the Twisted-Python mailing list