Bug 42317 - System.Net.Sockets.Socket.SetSocketOption returns "Invalid arguments" if I set SO_DEBUG = true
Summary: System.Net.Sockets.Socket.SetSocketOption returns "Invalid arguments" if I se...
Status: RESOLVED NORESPONSE
Alias: None
Product: Runtime
Classification: Mono
Component: io-layer (show other bugs)
Version: 4.5.X
Hardware: PC Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: marcos.henrich
URL:
Depends on:
Blocks:
 
Reported: 2016-07-01 13:30 UTC by Mikhail Filippov
Modified: 2017-10-11 17:25 UTC (History)
5 users (show)

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


Attachments

Description Mikhail Filippov 2016-07-01 13:30:17 UTC
System.Net.Sockets.Socket.SetSocketOption returns "Invalid arguments" if I set SO_DEBUG = true
at System.Net.Sockets.Socket.SetSocketOption (SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue) <0x10e962b50 + 0x000c1> in <filename unknown>:0 
    at AsyncIO.DotNet.NativeSocket.SetSocketOption (SocketOptionLevel optionLevel, SocketOptionName optionName, Int32 optionValue) <0x10e980df0 + 0x0003f> in <filename unknown>:0 
    at AsyncIO.AsyncSocket.set_NoDelay (Boolean value) <0x10e980da0 + 0x00037> in <filename unknown>:0
Comment 1 Alex Rønne Petersen 2016-08-29 08:41:41 UTC
Can you please provide a small test case that demonstrates the problem? I tried this:

> using System.Net.Sockets;
> class Program {
>     static void Main () {
>         var socket = new Socket (AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);
>         socket.SetSocketOption (SocketOptionLevel.Tcp, SocketOptionName.Debug, true);
>     }
> }

Which works fine with Mono master.
Comment 2 Mikhail Filippov 2016-08-29 11:29:55 UTC
It's flacky problem only on MacOS X. I don't have stable repro.
Comment 3 Rodrigo Kumpera 2017-10-11 17:25:09 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and reopen the bug report.

Thank you!

Note You need to log in before you can comment on or make changes to this bug.