Re: No crashlog & my application is leaving me :-(
Re: No crashlog & my application is leaving me :-(
- Subject: Re: No crashlog & my application is leaving me :-(
- From: Bill Bumgarner <email@hidden>
- Date: Tue, 13 Jun 2006 16:50:43 -0700
On Jun 13, 2006, at 3:48 PM, Buddy Kurz wrote:
Oh goody - more documentation to read....
A stagnant mind is lost in the swamp of boredom....
unfortunately I haven't been able to reproduce the crash locally -
how does one run a .app from the command line? The open command will
start it but just returns to the shell.
Inside the app wrapper is a standard executable. For example:
/Applications/TextEdit.app/Contents/MacOS/TextEdit
The above will run TextEdit in a shell.
So an unhandled (not a word) signal just aborts the application
while an exception will record something in the crash log?
A signal is not an exception. Signals are a low level unix mechanism
for interrupting the current execution of an application such that it
can deal with some kind of emergency call for service from somewhere
else. Exceptions don't interrupt execution. Instead, an exception
changes the return path of execution, bypassing stack frames until an
exception handler is hit.
Most signals can be handled in a signal handler -- a C function that
is called that can give indication that execution should resume as if
nothing happened.
More likely than not, you will want to simply ignore SIGPIPE as the
various socket calls made in your code will return error codes when
trying to read/write/close/seek/wait/connect to a pipe/socket that was
closed remotely....
Something like...
signal(SIGPIPE, SIG_IGN)
many thanks for the tip - it makes sense and give me a purpose again.
Heh. Happy to help.
b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden