This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients frohman, gregory.p.smith
Date 2010-12-19.22:02:47
SpamBayes Score 1.424142e-05
Marked as misclassified No
Message-id <1292796173.86.0.626601801335.issue8073@psf.upfronthosting.co.za>
In-reply-to
Content
In your back traces notice that the size= argument is clearly nonsensical.

Regardless, i can't reproduce this on any of my systems (I don't have a suse system of any sort).  If that is the only place you are seeing this I strongly suspect you've got something going on there.

Without some way to reproduce this or more detailed debugging info (point to the line of python that dies and single step into the C code in gdb from there printing out relevant state along teh way to see what happens) there is nothing I can do.
History
Date User Action Args
2010-12-19 22:02:54gregory.p.smithsetrecipients: + gregory.p.smith, frohman
2010-12-19 22:02:53gregory.p.smithsetmessageid: <1292796173.86.0.626601801335.issue8073@psf.upfronthosting.co.za>
2010-12-19 22:02:47gregory.p.smithlinkissue8073 messages
2010-12-19 22:02:47gregory.p.smithcreate