🚀 go-pugleaf

> *** malloc[278]: Deallocation of a pointer not malloced: 0xffffffff;
> This could be a double free(), or free() called with the middle of an
> allocated block; Try setting environment variable MallocHelp to see
> tools to help debug

I've seen this a lot, but not on 10.1.x. I'm using 10.0.4 and I see this 
whenever I try to free() a piece of memory that I've malloc()ed.

What I would do would be something like:

int *ptr1, *ptr2;

ptr1 = (char *)malloc( 100 * sizeof( int ) );
ptr2 = (char *)malloc( 200 * sizeof( int ) );

Now this would work alright until I freed one and tried to access the 
other as in:

free( ptr1 );
ptr2[1] = 10;     // your error appears at this point

This drove me crazy for a while and so I tried C++ new and delete and 
that worked without problem, and I could allocate and dealloc memory at 
will.

I looked into this some more just recently and I've noticed that this 
malloc problem goes away if you type cast when passing to free. I can't 
remember too well how it went but whenever you free()ed memory you 
needed to typecast in the following way:

free( (void *)ptr1 );
ptr2[123] = 11;   // this now works

I can't remember the cast exactly (it might be (char *) now that I think 
of it) but the fix to a bug that reports this error can be done in this 
way.

Weird that this bug is still in 10.1.x. I thought only oldies like 
myself had to suffer this.

Don't know if that helps,

Andrew