[Sablevm-developer] debbuggtk improvements and synchronization w/ gnu classpath
Brought to you by:
egagnon
From: Grzegorz B. P. <ga...@de...> - 2004-01-19 10:40:59
|
Hi! I've just tried to run things from debbuggtk and there's important improvement - it almost starts now. After a while I get: $ bugviewer (java-gnome:6261): Gtk-CRITICAL **: file gtkwidget.c: line 3690 (gtk_widget_grab_default): assertion `GTK_WIDGET_CAN_DEFAULT (widget)' failed [jni: fatal error (Local reference capacity exceeded)] Aborted $ bugwatcher [jni: fatal error (Local reference capacity exceeded)] Aborted (btw: shouldn't we give a stack backtrace at this point? it's not really helpful as this way it's hard to say where the problem actually can be) I am not sure whether this problem is in java-gnome itself or rather in GNU Classpath, but I believe I have seen some mails on GNU CP ML lately, that were about not using more local references than allowed. Or maybe somebody has a better idea where the problem could be? Anyway - can we synchronize our SVN w/ current upstream? Is there any documentation how to do this properly? We should also start pushing our changes back upstream. Cheers, Grzegorz B. Prokopski PS: Trying to run bugreporter I get sablevm: INTERNAL ERROR (source file "native_interface.c", line 23026): todo it's AllocObject (JNIEnv *_env, jclass cls) - so maybe it could be the next hole to target. -- Grzegorz B. Prokopski <ga...@de...> Debian GNU/Linux http://www.debian.org SableVM - LGPLed JVM http://www.sablevm.org Why SableVM ?!? http://devel.sablevm.org/wiki/WhySableVM |