It turns out that "glib"'s g_critical() facility, used to report serious problems, calls g_log(), which then goes ahead and calls the g_thread functions again. Which are the very ones that are trying to report the problem.
I've switched the error reporting in the --portable-native-sync back to using the equivalent of fprintf(stderr, ...).
I've also gone back to using old-fashioned assert() instead of glib's g_assert().
-- Steven Augart
Jikes RVM, a free, open source, Virtual Machine: http://oss.software.ibm.com/jikesrvm
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
