Malloc error

[mankoff]

Hi Group,

I'm brand spanking new to Python. Never coded in it, but I'm
comfortable coding in general in other languages. I'm Trying to get
some legacy code to run on a newer machine. I don't have access to the
legacy box for debugging.

I'm getting the following error:

Python(36979) malloc: *** error for object 0x88374: Non-aligned
pointer being freed
*** set a breakpoint in malloc_error_break to debug

My python version is:

$ python
Python 2.5.2 (r252:60911, Feb 22 2008, 07:57:53)
[GCC 4.0.1 (Apple Computer, Inc. build 5363)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
And this is on an Intel MacBook running 10.5.2

The error is getting printed hundreds of times until I CTRL+C at which
point I see:

Python(36979) malloc: *** error for object 0xa58074: Non-aligned
pointer being freed
*** set a breakpoint in malloc_error_break to debug
Traceback (most recent call last):
File "v2_to_bdb.py", line 104, in <module>
main()
File "v2_to_bdb.py", line 101, in main
fill_dbm(f, dbm, info, ids, sources)
File "v2_to_bdb.py", line 34, in fill_dbm
mystring = stationstring.serialize(dict, data)
KeyboardInterrupt

And advice on how to work around this error will be much appreciated.

Thanks,

-k.

 

[Gabriel Genellina]

I'm brand spanking new to Python. Never coded in it, but I'm
comfortable coding in general in other languages.
Welcome...!

I'm Trying to get
some legacy code to run on a newer machine. I don't have access to the
legacy box for debugging.

I'm getting the following error:

Python(36979) malloc: *** error for object 0x88374: Non-aligned
pointer being freed
*** set a breakpoint in malloc_error_break to debug

Ouch. I'd like to think that the error doesn't come from Python itself but
from some compiled C extension. Are you using any?
I'd try with the same Python version the legacy box had, if it was older
than 2.5.2

 

[mankoff]

Ouch. I'd like to think that the error doesn't come from Python itself but  
 from some compiled C extension. Are you using any?
I'd try with the same Python version the legacy box had, if it was older  
than 2.5.2

You're right. I was using some C extensions. The bug was there. I've
fixed it and everything appears to be working.

Thanks,

-k.