• 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: accept() does not behave the same in 32 and 64-bit on 10.6?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: accept() does not behave the same in 32 and 64-bit on 10.6?


  • Subject: Re: accept() does not behave the same in 32 and 64-bit on 10.6?
  • From: Quinn <email@hidden>
  • Date: Sat, 5 Sep 2009 23:38:47 +0100

At 15:36 +0200 31/8/09, Stéphane Sudre wrote:
Is it the expected behavior that accept() does not return the same type of sockets when it's run in 32 bit and 64-bit?

Clearly it wasn't expected by you (-:

Seriously though, like you, I wouldn't expect that. Rather, I would expect accept() to return a socket with the same non-blocking state as the listening socket you called it on. I verified this behaviour for both blocking and non-blocking listening sockets on both i386 and x86_64. This was on 10.5.8. I can't test it on other systems right now because I'm on a 777 somewhere over Minnesota as I write this (-:

If you explain more about the circumstances in which you're seeing this behaviour, I may be able to uncover more information.

S+E
--
Quinn "The Eskimo!"                    <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: luanchd plist won't load after restart
  • Next by Date: Re: accept() does not behave the same in 32 and 64-bit on 10.6
  • Previous by thread: Re: luanchd plist won't load after restart
  • Next by thread: Re: accept() does not behave the same in 32 and 64-bit on 10.6
  • Index(es):
    • Date
    • Thread