Re: NSPortCoder timed out, causes crash
Re: NSPortCoder timed out, causes crash
- Subject: Re: NSPortCoder timed out, causes crash
- From: "Shawn Erickson" <email@hidden>
- Date: Mon, 10 Sep 2007 09:24:49 -0700
On 9/10/07, Richard Salvatierra <email@hidden> wrote:
> I have a server/client test app using DO that sends the client values
> over a local network. If the client connection fails (the app quits/
> crashes/unplugged, etc.) and the server sends the client another
> message, the server app logs a [NSPortCoder
> sendBeforeTime:sendReplyPort:] timed out. Now, while running in
> xCode, the run log displays the time out message. If running the app
> outside of xCode, it crashes. The hard part is the crash does not
> create a crash log. Before I send the message to the DO, I Try/Catch.
> What causes the crash.
>
> @try {
> [remoteObject sendDictionary: object];
> }
> @catch (id theException) {
> NSLog(@"%@", theException);
> [remoteObject release];
> }
> @finally { }
Are you over releasing and/or attempting to use a dealloced reference
to remoteObject. It seems a little strange that you would release the
remote object in the case of an exception yet not in the normal case
(aka under @finally).
Anyway if it doesn't produce a crash log then likely the application
decided to abort (or exit early). This could imply that an exception
isn't be handled.
Anything in the console log when you run the application?
-Shawn
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden