Tips for debugging stack smash?

• Subject: Tips for debugging stack smash?
• From: Scott Ribe <email@hidden>
• Date: Wed, 02 Aug 2006 10:27:50 -0600
• Delivered-to: email@hidden
• Delivered-to: email@hidden
• Thread-index: Aca2UJiS12tWhyJDEduf0QAWyzjSrg==
• Thread-topic: Tips for debugging stack smash?
• User-agent: Microsoft-Entourage/11.2.5.060620

Sigh... I'm smashing the stack, leaving things where XCode doesn't show any
useful info when it breaks. Most cruel of all, enabling MallocDebug results
in my 100% reproducible crash test case running to completion every time.

Suggestions? Besides: write better code ;-)

-- 
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden

• Follow-Ups:
  • Re: Tips for debugging stack smash?
    • From: Lawrence Gold <email@hidden>
  • Re: Tips for debugging stack smash?
    • From: "Sean McBride" <email@hidden>
  • Re: Tips for debugging stack smash?
    • From: Cameron Hayne <email@hidden>

• Prev by Date: Re: stop new header from being added to copy files?
• Next by Date: Re: stop new header from being added to copy files?
• Previous by thread: Re: Linking in CW shared lib vs. Xcode framework
• Next by thread: Re: Tips for debugging stack smash?
• Index(es):
  • Date
  • Thread