[issue4379] Py_SAFE_DOWNCAST in FILE_TIME_to_time_t_nsec failing
report at bugs.python.org
Fri Nov 21 18:20:07 CET 2008
New submission from Kevin Watters <kevinwatters at gmail.com>:
After releasing a Py_DEBUG build to some users who were experiencing
problems, I noticed a pattern in some of the crash reports I got back:
The only way I can see _wassert being hit in FILE_TIME_to_time_t_nsec is
in the Py_SAFE_DOWNCAST used to downcast an __int64 to int.
Py_SAFE_DOWNCAST checks that there is equality between the casted and
non-casted values with Py_DEBUG enabled--maybe in this function we
should remove Py_SAFE_DOWNCAST?
I can't find a way to see the actual value for "in" before the assert is
hit--I'm unfamiliar with picking through minidumps with WinDbg, which
for some reason will show me the stack for these dumps when Visual
Studio won't. But if I need to investigate more about them I can.
title: Py_SAFE_DOWNCAST in FILE_TIME_to_time_t_nsec failing
versions: Python 2.5.3
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list