[Mono-bugs] [Bug 599488] Why SocketException with ErrorCode == 10035 means Operation timed out? It breaks .NET compatibility

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sun Apr 25 19:53:03 EDT 2010



Lex Li <lextudio at gmail.com> changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |NEW
       InfoProvider|lextudio at gmail.com          |

--- Comment #2 from Lex Li <lextudio at gmail.com> 2010-04-25 23:53:02 UTC ---
Hi Gonzalo,

Below is how to reproduce it,

1. Check out #SNMP Change Set 41774

2. Use xbuild to build SharpSnmpLib.sln.

3. Go to TestAgent/bin/Debug, open a prompt.

4. Use su to run mono snmpd.exe.

5. Click Disabled button so this application starts to monitor port 161 on all
incoming SNMP messages.

6. Then open SharpSnmpLib.sln in MonoDevelop.

7. Open the Unit Tests panel and go to TestGetRequestMessage.TestTimeOut test

8. Execute this test case.

The test case is simply that I send a UDP packet to a nonexisting IP address in
my network and expect a SocketException for timeout.

On Windows, a SocketException whose ErrorCode is 10060 is there, so #SNMP will
package it up to TimeoutException.

But on Mono/openSUSE, I receive a SocketException whose ErrorCode is 10035.
This breaks the test case.

I am not the only one who hits this issue, and you can check this StackOverflow


Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list