This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author hfuru
Recipients hfuru
Date 2010-11-04.12:49:00
SpamBayes Score 2.700054e-05
Marked as misclassified No
Message-id <1288874942.68.0.464773855859.issue10312@psf.upfronthosting.co.za>
In-reply-to
Content
Parser/intrcheck.c:intcatcher() can do FILE* operations, which can
deadlock if the interrupt happens while a FILE* operation on the same
FILE holds a mutex for the FILE.  I've seen this happen elsewhere.

It'd rather be a pity to remove Py_Exit(), so I suggest
switch(interrupted++) gets a case 3 or 4: which does _exit(1),
and 'interrupted = 0;' is moved there from case 2.

Also 'interrupted' should be volatile sig_atomic_t, and
the function should save/restore errno as in Issue 10311.

BTW, you could use strlen(message) instead of sizeof(message)-1.
History
Date User Action Args
2010-11-04 12:49:02hfurusetrecipients: + hfuru
2010-11-04 12:49:02hfurusetmessageid: <1288874942.68.0.464773855859.issue10312@psf.upfronthosting.co.za>
2010-11-04 12:49:00hfurulinkissue10312 messages
2010-11-04 12:49:00hfurucreate