[New-bugs-announce] [issue7428] Possible memory issue with optparse

Bill Spotz report at bugs.python.org
Thu Dec 3 17:47:28 CET 2009

New submission from Bill Spotz <wfspotz at sandia.gov>:

I develop python extension modules for Trilinos, a large scientific 
computing project:


Unit testing my extension modules under Mac OS X, I came across the 
following error messages after upgrading from gcc 4.0 to basically any 
higher version:

  python(65587) malloc: *** error for object 0x1715674: Non-aligned 
pointer being freed

Debugging the problem (which occurs for me in several places in several 
test scripts), the error was always being raised in the built-in C++ 


which indicated to me that the problem was really probably somewhere 
else, and just being triggered in the ostream operator.

Trying to isolate the problem in a smaller script, I was unable to 
reproduce the error until I added

  import optparse

By the same token, I was able to eliminate the problem in my test 
scripts by getting rid of "import optparse".  I have changed these 
scripts now to use getopt, and they are running without error, but I 
thought I would report this strange behavior.

I realize after all of this that the problem might not actually be with 
optparse, but it sure seems like a likely culprit.  I would be happy to 
work with someone to try to reproduce the error, and then hopefully 
such a python expert would be able to find the actual issue.

components: Extension Modules
messages: 95936
nosy: wfspotz
severity: normal
status: open
title: Possible memory issue with optparse
type: resource usage
versions: Python 2.6

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list