[Mono-bugs] [Bug 72240][Wis] Changed - Incorrect behaviour when the network is overloaded.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 8 Feb 2005 04:01:31 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by vguzev@yandex.ru.


--- shadow/72240	2005-02-05 10:01:07.000000000 -0500
+++ shadow/72240.tmp.1542	2005-02-08 04:01:31.000000000 -0500
@@ -101,6 +101,26 @@
 ------- Additional Comments From gonzalo@ximian.com  2005-02-05 10:01 -------
 I cannot reproduce this problem with current HEAD.
 On 1-0 branch, i get a segmentation fault in the server after the
 client finishes.
+------- Additional Comments From vguzev@yandex.ru  2005-02-08 04:01 -------
+Yesterday I installed mono-1.1.3 from source code and this sample 
+still doesn't work properly. But in this version it doesn't halt on 
+SEGFAULT - client just stops at some moment and wait for something 
+infinitely (After all data has been sent I think). So the problem 
+still remains - the attached sample doesn't work.
+Also in this new version the call of method Dns.GetHostName() leads 
+to termination of Environment.CommandLine variable! After this call 
+some garbage is assigned to this variable. The interesting thing is 
+that it works in simple examples like this:
+Console.WriteLine( Dns.GetHostName() );
+Console.WriteLine( Environment.CommandLine );
+Now this bug appears constantly in our MC# Runtime which use a lot 
+of features like Reflection, Threading and etc. But yesterday I 
+couldn't find a small example that reproduce this problem yet... 
+Hope today I'll find it.