| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
| Hi Mark - I appreciate your familiarity with your own code, but... On Oct 26, 2005, at 11:17 AM, Mark D. Gerl wrote:
That's a dangerous attitude. You should be excited to try something already installed on your system, which could potentially track down your bug quickly and without the hassle or delay of waiting for mailing list responses. The response you've gotten here sort of hints at the fact that "Mach-O projects don't just crash themselves." I also strongly recommend trying "Guard Malloc," which is a much more accurate (and painstakingly slow) tool for detecting overruns. I don't know how easy it is to do outside of Xcode, but it is great for catching "Oh my gosh, I didn't *think* I had any memory stompers!" bugs. I think it sends the wrong message when you enter a desperate plea for help to a mailing list, and then to follow up with expressions mild dismissal when people offer good suggestions. Good luck catching this bug! Daniel |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Carbon-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/carbon-dev/email@hidden This email sent to email@hidden
| References: | |
| >CFM to Mach-O Conversion Crash in CodeWarrior (From: "Mark D. Gerl" <email@hidden>) | |
| >Re: CFM to Mach-O Conversion Crash in CodeWarrior (From: John Stiles <email@hidden>) | |
| >Re: CFM to Mach-O Conversion Crash in CodeWarrior (From: "Mark D. Gerl" <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.