How do I set it up to do that? I doubt I have
And that is just the default main.m that comes when you start a new app
Main Topics
Browse All TopicsI need help debugging this crash, unfortunately the crash log doesn't give me enough data to understand where the problem is in my code. I'm not asking for a solution, but what next steps should I be taking to debug?
To my understanding it looks like NSLog is trying to print out an object but fails as the object passed isn't actually an object. But I literally have around 300 NSLogs in my app so it's difficult to track down where I screwed something up. My thought is I probably released an object too soon and it's pointing to crap, so it crashes - how can I find this?
I've tried the NSZombie method, but unfortunately the address printed to the console (of the object that disappeared) is NEVER an address of an object in Instruments. I'm on Snow Leopard if that helps any.
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Sorry the crash is not in 10000 line of code it's in one place you can step through main and see where it happens. You can step over function call if you like and you can follow them. There must be at least some pointer where your program starts to crash.
at least some code in main is running because the bactrace says so
0x0000227c main + 90 (main.m:35)
So the program starts runing and crashes after some function calls.
Regards
Friedrich
Now that is completely different information. You did just wrote the program crashes. Not when and that the program still was running.
Then you have to change the whole stuff. You probably need to wrap all loggin into another method if you think that Logging is the problem.. Or you can remove all logging and see if that realyl is the cause for the crash.
Or if that is possible you register an Error handler for your program which just watches for the mentioned
EXC_BAD_ACCESS (SIGSEGV). Maybe you can catch it an write a backtrace for it.
Friedrich
Business Accounts
Answer for Membership
by: fridomPosted on 2009-10-14 at 22:08:50ID: 25577408
What is around here?
(main.m:35)
Have you set XCode such that is runs into the debugge on any non handeled exception?
Regards
Friedrich