[Mono-bugs] [Bug 74713][Maj] Changed - System.IO.IOException: Invalid handle to path "/tmp/tmp4d062ea3"

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sun, 24 Apr 2005 20:32:48 -0400 (EDT)

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 flashdict@gmail.com.


--- shadow/74713	2005-04-24 20:13:54.000000000 -0400
+++ shadow/74713.tmp.23438	2005-04-24 20:32:48.000000000 -0400
@@ -96,6 +96,35 @@
 ------- Additional Comments From flashdict@gmail.com  2005-04-24 19:41 -------
 What operating system are you using there?  Since you are not
 specifying it on the form here, I assume it's something unusual?
 ------- Additional Comments From bmaurer@users.sf.net  2005-04-24 20:13 -------
 It's Linux. I have one box with fc3 and another with NLD.
+------- Additional Comments From flashdict@gmail.com  2005-04-24 20:32 -------
+I see.  Well, that's definitely supported.  :) 
+Well, here's a (edited for brevity) gdb trace of the problem I'm
+seeing when running this testcase, in case it might be helpful:
+#4  0x283fdde4 in abort () from /lib/libc.so.6
+#5  0x281e7af3 in g_logv () from /usr/local/lib/libglib-2.0.so.600
+#6  0x281e7b84 in g_log () from /usr/local/lib/libglib-2.0.so.600
+#7  0x281e7c33 in g_assert_warning () from
+#8  0x080ce9aa in _wapi_handle_unref (handle=0x2834dbcc) at handles.c:940
+#9  0x080cebe3 in CloseHandle (handle=0x6) at handles.c:1053
+#10 0x080ab911 in ves_icall_System_IO_MonoIO_Close (handle=0x6,
+error=0xbf5e9eac) at file-io.c:540
+#50 0x0818b2ac in __JCR_LIST__ ()
+#54 0x080a948c in thread_adjust_static_data (thread=0x0) at threads.c:2167
+Previous frame inner to this frame (corrupt stack?)
+In this case, after about 180 executions of the loop by the five
+threads.  I have no idea if the problem I'm seeing can be related to
+the exception that is being seen on your platform, but it _feels_ like
+this may be a good case.  I wonder how OSX is handling this...