• 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: Exited abnormally: Broken pipe
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Exited abnormally: Broken pipe


  • Subject: Re: Exited abnormally: Broken pipe
  • From: Jens Alfke <email@hidden>
  • Date: Sun, 17 Feb 2008 14:44:38 -0800


On 17 Feb '08, at 11:35 AM, Kyle Sluder wrote:

You're trying to read write to a pipe fd that has been closed on you.
Trap SIGPIPE (man 3 signal) and you'll get a better understanding of
where this is happening.

SIGPIPE is widely considered a nuisance. Many programs call signal(2) at startup to ignore that signal completely. Just be sure to check errno after a failed read/write, to detect when the socket got closed from underneath you.


—Jens_______________________________________________

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


References: 
 >Exited abnormally: Broken pipe (From: Tomas Franzén <email@hidden>)
 >Re: Exited abnormally: Broken pipe (From: "Kyle Sluder" <email@hidden>)

  • Prev by Date: Re: [Foo new] vs [[Foo alloc] init]:
  • Next by Date: Re: A couple questions relevant to games
  • Previous by thread: Re: Exited abnormally: Broken pipe
  • Next by thread: Re: Cocoa-dev Digest, Vol 5, Issue 255
  • Index(es):
    • Date
    • Thread