Need help on iphone crash log. Any experts around?

Looks like you're crashing at mach_msg_trap the function that handles Objective-C message passing. This is often a sign that you're doing one of two things.

Looks like you're crashing at mach_msg_trap, the function that handles Objective-C message passing. This is often a sign that you're doing one of two things: You have a memory management issue somewhere - you're trying to call a selector on an object that's already been released, you're overreleasing an object, or something similar. You're not being thread-safe in some framework.

This can be especially tricky in UIKit (most of the UI* elements that the iPhone uses), where you're not allowed to update the screen from any thread other than the main thread. Look at using Instruments to check your object allocation and leaks, and double-check that you're respecting thread safety properly.

Amazing answer! Thanks a lot! I'll try some stuff out.

I'm pretty sure it has something to do with the thread safe in UIKit. Any ideas on how preventing this or best practices on being thread safe when using UIKit? For example: if I do someUITableView reloadData I should ensure that it's executed by the main thread, right?

– nico Jul 10 '09 at 3:47 Pretty much. The idea is that you shouldn't be calling or committing anything that will cause an animation (in a table view, this means reloading data, inserting/deleting rows/sections) from anywhere other than the main thread. If your app is single-threaded, no worries; otherwise, just use the performSelectorOnMainThread: method.

– Tim Jul 10 '09 at 4:10.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.