Author sadit
Recipients sadit
Date 2008-06-25.17:27:50
SpamBayes Score 0.000887225
Marked as misclassified No
Message-id <>

I found a rare bug in heavy multithreading IO operations. The bug arises
under a stupid sequence of I/O operations. The sequence is not a normal
one, but the real problem is that the Python's interpreter crashes. The
correct behavior should be raise an IOError exception (I think).

The bug occurs when some thread closes a file or socket whilst other
thread tries to read or write from the same socket. The failure it's
inside the fileobject.c because tries to read or write the specified
data size inside a loop without check in every iteration if the object
is closed (it checks only outside the loop). The file object is set to
NULL and a SIGSEGV happens.

I'm a python developer (in the language, but not developer of the
language), so i really don't know anything about the best way to solve
this issue, and how the project it's managed. I can develop an script to
raise this bug if anyone it's interested in this problem. I'm already
owns one, but I don't find it, and the real program that arises the
error was rewritten so i don't have it.


Eric Sadit
Date User Action Args
2008-06-25 17:27:53saditsetspambayes_score: 0.000887225 -> 0.000887225
recipients: + sadit
2008-06-25 17:27:53saditsetspambayes_score: 0.000887225 -> 0.000887225
messageid: <>
2008-06-25 17:27:51saditlinkissue3200 messages
2008-06-25 17:27:50saditcreate