Bug 12193 - System.Net.Sockets.Socket SendToAsync not work in epoll
Summary: System.Net.Sockets.Socket SendToAsync not work in epoll
Alias: None
Product: Runtime
Classification: Mono
Component: io-layer ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-05-10 09:16 UTC by changyu
Modified: 2018-01-24 17:59 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

the capture of strace (32.32 KB, image/jpeg)
2013-05-10 09:16 UTC, changyu

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description changyu 2013-05-10 09:16:29 UTC
Created attachment 3944 [details]
the capture of strace

when using System.Net.Sockets.Socket to create a async socket, run strace on the server,perhaps it was run in poll, not epoll, my application run on centos 6.3, mono version is 3.0.7, for detail you can get the attachment.
Comment 1 Rodrigo Kumpera 2017-10-14 00:10:00 UTC
Thank you for your report!

It appears you are running a very old version of Mono. Could you please try to update to any recent version and try to reproduce the issue again.

If the issue still persists please include the version information and change the bug status to NEW.
Comment 2 Ludovic Henry 2018-01-24 17:59:31 UTC
Please provide information requested in previous comment to reopen. Thank you.