• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: No crashlog & my application is leaving me :-(
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: No crashlog & my application is leaving me :-(


  • Subject: Re: No crashlog & my application is leaving me :-(
  • From: Buddy Kurz <email@hidden>
  • Date: Tue, 13 Jun 2006 15:48:37 -0700

Bill,

Oh goody - more documentation to read....

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.

So an unhandled (not a word) signal just aborts the application while an exception will record something in the crash log?

many thanks for the tip - it makes sense and give me a purpose again.

buddy



On Jun 13, 2006, at 3:10 PM, Bill Bumgarner wrote:

On Jun 13, 2006, at 2:58 PM, Buddy Kurz wrote:
My application is a server that accepts connections from network clients and handles each with a separate thread. It seems to function perfectly but periodically just drops everybody and goes away. I have an NSLog(...) in applicationShouldTerminate: that is not recording anything and there is nothing in the console log. It just goes away. (aarrrrrrggghhh!!) It doesn't appear to be leaking memory. If I quit the application, it politely shuts down it's connections and records properly in the console log.

What I need is some hint on how to track down the cause.

Is there something I don't understand here? Can an application go down without creating a crashlog or calling applicationShouldTerminate:?

Sounds like your app is getting taken out by a signal. SIGPIPE, most likely.


Run it at the command line and then reproduce the crash, if possible. The app will likely terminate with a "broken pipe" message.

This happens when you try to read from or write to a socket when the other side has closed the connection.

See 'man signal' for more info.

And, of course, it may be something completely different.

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
  • Follow-Ups:
    • Re: No crashlog & my application is leaving me :-(
      • From: Bill Bumgarner <email@hidden>
References: 
 >No crashlog & my application is leaving me :-( (From: Buddy Kurz <email@hidden>)
 >Re: No crashlog & my application is leaving me :-( (From: Bill Bumgarner <email@hidden>)

  • Prev by Date: LSIsAppleDefaultForType
  • Next by Date: Re: Launch another app without losing focus
  • Previous by thread: Re: No crashlog & my application is leaving me :-(
  • Next by thread: Re: No crashlog & my application is leaving me :-(
  • Index(es):
    • Date
    • Thread