traceback parameter is None in __excepthook
7 views
Skip to first unread message
Dustin Spicuzza
Oct 1, 2011, 2:42:06 AM10/1/11
to Winpdb
Causes winpdb to crash. By commenting out lines 13915 and 13196 in
rpdb2.py, it no longer crashes and alerts the user to an unhandled
exception, but the exception is apparently not available in analysis
mode. You can see a call stack, but you cannot bring up the source for
any of the frames because of the following error:
*** Command returned the following error:
*** <type 'exceptions.TypeError'>, unsupported operand type(s) for -:
*** 'NoneType' and 'int'.
*** Please check stderr for stack trace and report to support.
It should be noted that the exception is raised when importing the
_gst module (windows python bindings for gstreamer), so perhaps that
is why there isn't a traceback object?
Using python 2.7 on windows XP SP3.
rpdb2.py, it no longer crashes and alerts the user to an unhandled
exception, but the exception is apparently not available in analysis
mode. You can see a call stack, but you cannot bring up the source for
any of the frames because of the following error:
*** Command returned the following error:
*** <type 'exceptions.TypeError'>, unsupported operand type(s) for -:
*** 'NoneType' and 'int'.
*** Please check stderr for stack trace and report to support.
It should be noted that the exception is raised when importing the
_gst module (windows python bindings for gstreamer), so perhaps that
is why there isn't a traceback object?
Using python 2.7 on windows XP SP3.
Reply all
Reply to author
Forward
0 new messages