Re: malloc/free problems within a thread

FROM : Ken Tozier
DATE : Sat Jul 29 23:50:42 2006

Well here are a couple of the errors I'm seeing

PMServer X(21089,0x1863800) malloc: *** error for object 0x1861c00: 
incorrect checksum for freed object - object was probably modified 
after being freed, break at szone_error to debug
PMServer X(21089,0x1863800) malloc: *** set a breakpoint in 
szone_error to debug

I set the breakpoint as suggested but the debugger seems to be 
basically worthless. It keeps throwing up this error ""MyApp exited 
with status (1). The Debugger is still running. Use "Restart" to 
debug again". Problem is though the restart button is grayed out and 
the debugger it isn't in fact doing anything when I get this message. 
I submitted a debugger specific question related to this on XCode forum.

It seems like the NSAutorelease pool destroys all objects created 
within it regardless of whether they have a retain or not. That's the 
only thing I can think of. Is that what it does?



On Jul 29, 2006, at 4:47 PM, Ken Tozier wrote:

> Hi
>
> I have a process that spawns threads and inside these threads I 
> malloc/free some memory but I'm getting either "xxx has exited due 
> to signal 11 (SIGSEGV)" or "sigbus 10" errors. I know from past 
> experience that these most likely indicate a non-retained object, 
> problem is though that I checked very carefully and everything that 
> I want to keep around is definitely retained. Could the fact that 
> some objects were created inside a thread's NSAutorelease alloc/
> release override the retain commands?
>
> Thanks
>
> Ken
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list      (<email_removed>)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/kentozier%
> 40comcast.net
>
> This email sent to <email_removed>