It might be. The os installed this version of python not me. If my memory serves me correctly I saw something like this in an older release of python 2.5 that was later fixed. I bet that is it. Let me see if that is the problem.
On 7/11/07, Gustavo Niemeyer <[EMAIL PROTECTED]> wrote: > Hey Noah, > > > In [2]: class Person(object): > > ...: __storm_table__ = "person" > > Python(10525) malloc: *** error for object 0x559df4: Non-aligned > > pointer being freed > > *** set a breakpoint in malloc_error_break to debug > > Python(10525) malloc: *** error for object 0x559dec: Non-aligned > > pointer being freed > > *** set a breakpoint in malloc_error_break to debug > > ...: > > Wow! Weird.. Storm has no C extensions nor it uses any dirty > tricks, so it can't be a problem with it. I'm curious if it > might actually be something on Python itself in that > environment. > > -- > Gustavo Niemeyer > http://niemeyer.net > -- http://www.blog.noahgift.com -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
