Message159909
> TBH I don't understand why it should crash, and therefore how your patch
> helps. Trying again using narrow strings should always work; indeed, the
> code did that before I touched it. Can you describe how it crashes?
The important part of the patch is the removal of the "!" in
if (!utime_read_time_arguments(&ua)) {
Without that change, if utime_read_time_arguments(&ua) fails then the unicode path is wrongly chosen. Then PyUnicode_AsUnicode(upath) is called when upath has not been initialized. |
|
Date |
User |
Action |
Args |
2012-05-04 07:51:55 | sbt | set | recipients:
+ sbt, gvanrossum, loewis, gregory.p.smith, ncoghlan, pitrou, vstinner, larry, eric.araujo, Arfrever, r.david.murray, maubp, shaurz, rosslagerwall, python-dev |
2012-05-04 07:51:55 | sbt | set | messageid: <1336117915.61.0.922507312184.issue14127@psf.upfronthosting.co.za> |
2012-05-04 07:51:55 | sbt | link | issue14127 messages |
2012-05-04 07:51:54 | sbt | create | |
|