[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2015-10-12 Thread Martin Panter
Changes by Martin Panter : -- Removed message: http://bugs.python.org/msg185910 ___ Python tracker ___

[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2013-04-03 Thread Richard Oudkerk
Richard Oudkerk added the comment: Adding PyErr_CheckSignals() after PyOS_Readline() in builtin_input() seems to fix the problem. -- Added file: http://bugs.python.org/file29665/input-ctrlc.patch ___ Python tracker rep...@bugs.python.org

[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2013-04-03 Thread Richard Oudkerk
Changes by Richard Oudkerk shibt...@gmail.com: Removed file: http://bugs.python.org/file29665/input-ctrlc.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13673 ___

[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2013-04-03 Thread Richard Oudkerk
Richard Oudkerk added the comment: Sorry, last message was for another issue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13673 ___ ___

[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2012-01-08 Thread sbt
sbt shibt...@gmail.com added the comment: Trivial 3 lines patch. I guess there is still a race: if Ctrl-C is pressed after PyErr_CheckSignals() is called but before PyObject_Str() then the printing of any exception can still be suppressed. -- Added file:

[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2011-12-29 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: I think calling PyErr_WriteUnraisable would be more appropriate than PyErr_Clear. I also wonder whether it's ok to ignore the exception. Pressing e.g. Ctrl-C generally shouldn't fail to stop the program, even if another exception is being

[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2011-12-29 Thread sbt
sbt shibt...@gmail.com added the comment: Attached is a patch for the default branch. Before calling PyFile_WriteString() the patch saves the current exception. Then it calls PyErr_CheckSignals() and clears the current exception if any. After calling PyFile_WriteString() the exception is

[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2011-12-29 Thread sbt
sbt shibt...@gmail.com added the comment: I think I have found the problem. PyTraceBack_Print() calls PyFile_WriteString(), which calls PyFile_WriteObject(), which calls PyObject_Str() which begins with PyObject_Str(PyObject *v) { PyObject *res; if (PyErr_CheckSignals())

[issue13673] PyTraceBack_Print() fails if signal received but PyErr_CheckSignals() not called

2011-12-29 Thread sbt
sbt shibt...@gmail.com added the comment: I think calling PyErr_WriteUnraisable would be more appropriate than PyErr_Clear. You mean just adding PyErr_CheckSignals(); if (PyErr_Occurred()) PyErr_WriteUnraisable(NULL); before the call to PyFile_WriteString()? That seems to