C socket bad file descriptor




















Existing Members Sign in to your account. This email is in use. Do you need your password? Submit your solution! When answering a question please: Read the question carefully. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem.

Insults are not welcome. Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question. Let's work to help developers, not make them feel stupid.

Related Questions. Your technique of only printing error messages in debug mode seems to me complete madness, and in any case calling another function between a system call and perror is invalid, as it may disturb the value of errno. Indeed it may have done so in this case, and the real underlying error may be different. How are we doing? Please help us improve Stack Overflow.

Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 9 years, 6 months ago.

Active 2 years, 5 months ago. Viewed k times. Can you have any idea about the reason of the error? Improve this answer. Thank you, it works now! Does this mean that the windows socket API isn't implemented the same way as the linux sockets? As in, are my socket variables really file descriptors or just an identifier specifically made for winsock?

Is anything really a file descriptor on Windows, or is it all just a pile of kludges pretending to be a file descriptor? You have a point. But then are all those kludges the same type of kludge?

Are sock and stdin the same type of thing, and if not how do they differ? Somehow this situation failed to improve when winsock became part of the OS. Sign up or log in Sign up using Google. Sign up using Facebook.

Sign up using Email and Password. Yes, you're right that the description is unclear. The stack is to small for all the IP stacked on IP. That's great, thanks for your help.

I don't think I could've solved it myself. I'll patch the Makefile and wait for the PRs to be merged. Thanks again! Sign up for free to join this conversation on GitHub.

Already have an account? Sign in to comment. Area: network Area: pkg Type: bug. Linked pull requests.



0コメント

  • 1000 / 1000