On 05/04/02 Linus Upson wrote: > I'm having a problem running the corlib tests in mono on Windows. Things > go fairly well until a certain point where the CPU goes to 100% for a > few seconds and then the mono process exits with no error message. A > file called gc.log is created in the current directory. For example:
Who creates this gc.log file? > DROPOUT 280$ mono NUnitConsole_mono.exe > MonoTests.AllTests,corlib_linux_test.dll > ......................................... > ..E.F...................................... > ............................F............. > ......................F.......F.......E.F.F... > .....DROPOUT 281$ > DROPOUT 281$ > DROPOUT 281$ cat gc.log > Needed to allocate blacklisted block at 0x17da000 This is a warning. You could run mono in a debugger and check why it exits. lupus -- ----------------------------------------------------------------- [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
