-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python test suite is failing on 32 bit builds (MinGW32, Cygwin32, Linux) #562
Comments
Making steady progress. Solved 1. 3 more to solve:
|
I've been over #262 very carefully on 32 bit linux. I think there's a crashing issue in vsnprintf on 32 bit systems. I've written the following test program:
It's odd. We don't need the (size_t) cast the first time. This issue has something to do with 64 bit integers on the stack going to va_start.
I've been over every call to stringFormat() and added (size_t) casts if there is any possibility of the 64bit integer being passed. I still have to investigate #73 #74 and #75. I think we're throwing an arithmetic exception on a 32 bit processor and never reach our kerCorruptedMetadata. I'll find that tomorrow. Meanwhile, I've submitted a fix for #266 on 32 bit systems. |
I suspected those three issues were instances of the same fault on 32 bit systems. Here's the fix:
We're processing a fuzzed file and we detect a 32 bit overflow on a 32 bit system and throw kerArithmeticOverflow. 64 bit systems will throw kerCorruptedMetadata. The test harness expects Result: 32 and 64 bit systems behave the same. |
I suspect this is because the reference output reports 64bit integers.
The text was updated successfully, but these errors were encountered: