Message146929
Let's take an example: on a 32bit system, call
_PyString_Resize(&s, 0x7ffffff8)
Then PyStringObject_SIZE + newsize is something like -0x7ffffff8 (yes, it wraps around and is a negative number)
But when cast to an unsigned size_t (because that's what PyObject_REALLOC declares as parameter), it becomes 0x80000008, which is correct even if it is very likely to fail.
Did you experience something different? |
|
Date |
User |
Action |
Args |
2011-11-03 13:02:37 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, asdfasdfasdfasdfasdfasdfasdf |
2011-11-03 13:02:37 | amaury.forgeotdarc | set | messageid: <1320325357.93.0.0614294169255.issue13334@psf.upfronthosting.co.za> |
2011-11-03 13:02:37 | amaury.forgeotdarc | link | issue13334 messages |
2011-11-03 13:02:37 | amaury.forgeotdarc | create | |
|