Hi Martin,
Thanks for the suggestion!
Believe it or not, it ended up being a for loop overwriting memory under a very
specific condition.
This would cause a malloc to be corrupted, (for instance.)
Nothing like a wild goose chase. I looked everywhere for this one.
Best Regards,
bob.
On Jan 3,
Hi Robert,
> I seem to be crashing with the following message:
> malloc: *** error for object 0x104839c08: incorrect checksum for freed object
> - object was probably modified after being freed.
> *** set a breakpoint in malloc_error_break to debug
>
> However, malloc_error_break never gets call
Perhaps some eagle-eye out there can spot something I am not seeing..
Here is another ALLOC/FREE log message I get:
ALLOC 0x10306aa00-0x10306ae97 [size=1176]: thread_7fff737ac960 |start | main |
NSApplicationMain | -[NSApplication run] | -[NSApplication
nextEventMatchingMask:untilDate:inMode:de
Hi Everyone,
I seem to be crashing with the following message:
malloc: *** error for object 0x104839c08: incorrect checksum for freed object -
object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
However, malloc_error_break never gets called.
I have