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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=81729 --- shadow/81729 2007-05-25 06:10:00.000000000 -0400 +++ shadow/81729.tmp.21184 2007-05-25 08:47:32.000000000 -0400 @@ -47,6 +47,21 @@ ------- Additional Comments From [EMAIL PROTECTED] 2007-05-25 06:09 ------- Correct me if I'm wrong, but isn't monow.exe windows only? I'm having this problem both on Windows and Linux. + +------- Additional Comments From [EMAIL PROTECTED] 2007-05-25 08:47 ------- +You're right, of course. Since you didn't mention the OS, I simply +assumed Win32, where this issue is originating from. + +There are 2 ways to solve the this under unix: closing stdin +when the main assembly's target is "winexe". This has the drawback +that p/invoked unmanaged libs relying on stdin might break. + +The 2nd way is to solve this in managed code (using a NullStream +in Console.cs) with the drawback that p/invoked unmanaged libs +could still block the app while trying to read from stdin. + +(IMHO, we should not introduce this limitation in unix at all). + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
