Hmm, looks like I can repro anymore after updating again. El dc 07 de 05 del 2008 a les 04:24 +0200, en/na Lluis Sanchez Gual va escriure: > I updated mono to HEAD and now MonoDevelop eats all CPU when running. I > think this is caused by the InotifyWatcher code, since if I define > MONO_MANAGED_WATCHER=1 everything works fine. > > This is the managed stack trace of the thread waiting on the watcher: > > > "" tid=0x0x47432b90 this=0x0x488678: > at (wrapper managed-to-native) System.IO.InotifyWatcher.ReadFromFD > (intptr,byte[],intptr) <0x00004> > at (wrapper managed-to-native) System.IO.InotifyWatcher.ReadFromFD > (intptr,byte[],intptr) <0xffffffff> > at System.IO.InotifyWatcher.Monitor () [0x00010] > in /home/lluis/work/mcs/class/System/System.IO/InotifyWatcher.cs:369 > at (wrapper runtime-invoke) System.Object.runtime_invoke_void > (object,intptr,intptr,intptr) <0xffffffff> > > And this is the stack trace shown by gdb. That > mono_thread_interruption_checkpoint_request call looks weird to me. > > #0 0xffffe410 in __kernel_vsyscall () > #1 0x4020203b in read () from /lib/libc.so.6 > #2 0x4639d7fd in ?? () > #3 0xffffffff in ?? () > #4 0x007ae010 in ?? () > #5 0x00001000 in ?? () > #6 0x408b40aa in ?? () > #7 0x007ae010 in ?? () > #8 0x0943dcf0 in ?? () > #9 0x0943dcf0 in ?? () > #10 0x081008c3 in mono_thread_interruption_checkpoint_request ( > bypass_abort_protection=-9) at threads.c:3449 > #11 0x4639d71c in ?? () > #12 0xffffffff in ?? () > #13 0x007ae000 in ?? () > > > Any clue? > Lluis. > > > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list