Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Trouble tracking down a crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Trouble tracking down a crash

Subject: Re: Trouble tracking down a crash
From: Chris Hanson <email@hidden>
Date: Tue, 18 Sep 2007 10:49:56 -0700

On Sep 18, 2007, at 10:41 AM, Thomas Engelmeier wrote:

Am 18.09.2007 um 19:29 schrieb Todd Blanchard:
My app crashes on exit with a memory access violation in objc_msgsnd (however it is spelled) - it seems to think the number 4 is a pointer somewhere. The debugger is of little help - it has no stack information to show me and provides no context information at all.
Potentially your stack is hosed. Use google for MALLOC_DEBUG, NSZombieEnabled and CFZombieLevel.

Don't forget libgmalloc. It can be very useful for debugging overwrites, underwrites, writes to freed blocks, etc. The libgmalloc(3) man page <x-man-page://3/libgmalloc> will tell you all about it and what options you can use with it. There's also a hook in Xcode (in the Executable inspector) where you can tell it to run an executable using libgmalloc.

  -- Chris

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



References:  
  >Trouble tracking down a crash (From: Todd Blanchard <email@hidden>)
  >Re: Trouble tracking down a crash (From: Thomas Engelmeier <email@hidden>)




Prev by Date:
Re: Trouble tracking down a crash

Next by Date:
Recovering a list of selectors to which an object can respond

Previous by thread:
Re: Trouble tracking down a crash

Next by thread:
Recovering a list of selectors to which an object can respond

Index(es):

Date
Thread