Re: Crashes and logfiles
Re: Crashes and logfiles
- Subject: Re: Crashes and logfiles
- From: Karl Kuehn <email@hidden>
- Date: Fri, 16 Jan 2004 16:11:07 -0500
An easy way of getting the messages that your app might be screaming
as it dies is to fire it up from the terminal. Here is an example for
Mail.app:
yourComputer% /Applications/Mail.app/Contents/MacOS/Mail
The executable will always be inside the .app package at
Contents/MacOS/<<Your-App-Name>>.
Often if the app crashes it will write something back to either stdin
or stderr, both of which are routed by default to terminal. There is
also a chance that it could have written something to:
/var/log/system.log
My guess is that you are using a framework that is not on their
system, or have a packaged permissions problem, both of which would
probably give a nice error message on stderr.
Karl Kuehn
email@hidden
On Jan 16, 2004, at 3:34 PM, Michael Becker wrote:
Maybe this is a stupid question, but my app runs nicely on my computer
but crashes on my customers machine (and *yes*, I compiled it using
"Deployment" style ;-), without ZeroLink turned on). The icon pops up
in the dock and then instantly disappears again.
Now my question: How can I check on my costumers machine what went
wrong? Does the system log the error messages? If so, where do I find
them? What is the common way of debugging this kind of crash?
Maybe this is more a general Mac OS X question than a Cocoa one, but I
figured you guys might easily know this stuff :-)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.