diff options
author | Fred Drake <fdrake@acm.org> | 2000-06-30 16:18:57 (GMT) |
---|---|---|
committer | Fred Drake <fdrake@acm.org> | 2000-06-30 16:18:57 (GMT) |
commit | 4c82b2366ff2eb38f062fc5da1b15ddd1c01fa4b (patch) | |
tree | 9706525a1647754a3d5aed1ba183b4544acaaebe /Python/traceback.c | |
parent | 4358b2c928e756a77613da7cb8c57676e8872935 (diff) | |
download | cpython-4c82b2366ff2eb38f062fc5da1b15ddd1c01fa4b.zip cpython-4c82b2366ff2eb38f062fc5da1b15ddd1c01fa4b.tar.gz cpython-4c82b2366ff2eb38f062fc5da1b15ddd1c01fa4b.tar.bz2 |
Trent Mick <trentm@activestate.com>:
This patch fixes possible overflow in the use of
PyOS_GetLastModificationTime in getmtime.c and Python/import.c.
Currently PyOS_GetLastModificationTime returns a C long. This can
overflow on Win64 where sizeof(time_t) > sizeof(long). Besides it
should logically return a time_t anyway (this patch changes this).
As well, import.c uses PyOS_GetLastModificationTime for .pyc
timestamping. There has been recent discussion about the .pyc header
format on python-dev. This patch adds oveflow checking to import.c so
that an exception will be raised if the modification time
overflows. There are a few other minor 64-bit readiness changes made
to the module as well:
- size_t instead of int or long for function-local buffer and string
length variables
- one buffer overflow check was added (raises an exception on possible
overflow, this overflow chance exists on 32-bit platforms as well), no
other possible buffer overflows existed (from my analysis anyway)
Closes SourceForge patch #100509.
Diffstat (limited to 'Python/traceback.c')
0 files changed, 0 insertions, 0 deletions