-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
samples/net/sockets/socketpair does not run as expected #52360
Comments
@rymaj - can you please update the upstream commit in the bug report? |
It's kind of a PITA to have to jump through all of the hoops and enable a network device just to use socketpair, which really shouldn't require any kind of network interface at all. Even just trying to run the sample application, I get an error:
|
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Actually, it seems at some point, |
The output below:
Indicates to me that the socket is not operating in blocking mode. However, it was opened in blocking mode (by default), so this is potentially a bug in the sockets implementation. I'm still working through it though, so will report more information as I find it. |
Describe the bug
I tried to run samples/net/socket/socketpair, and got the folllowing issue first,
Then I figure out I need to increase the default CONFIG_POSIX_MAX_FDS from 4 to 8 for 3 socket pairs (should this change be covered in socketpair/prj.conf ?)
Even I add this setting, I saw this issue, seems the poll mechanism was broken?
Please also mention any information which could help others to understand
the problem you're facing:
specific commit?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Impact
What impact does this issue have on your progress (e.g., annoyance, showstopper)
Logs and console output
If applicable, add console logs or other types of debug information
e.g Wireshark capture or Logic analyzer capture (upload in zip archive).
copy-and-paste text and put a code fence (```) before and after, to help
explain the issue. (if unable to obtain text log, add a screenshot)
Environment (please complete the following information):
Additional context
Add any other context that could be relevant to your issue, such as pin setting,
target configuration, ...
The text was updated successfully, but these errors were encountered: