[Sablevm-developer] Re: Bug#164363: libsablevm-native1: UnsatisfiedLinkError when using AWT
Brought to you by:
egagnon
From: Grzegorz P. <gr...@se...> - 2002-10-15 22:37:57
|
W li=B6cie z pon, 14-10-2002, godz. 12:57, Toby Speight pisze:=20 > With my patch, the GTK and GThread libraries are (dynamically) linked > in to satisfy dependencies on gdk_threads_mutex, gdk_root_window, > gthread_init, etc.: [...] > Yes, that's exactly the issue this patch solves. :-) OKay, it kinda worked, but now I am getting this (1.0.4): XXXXXXX TestAWT.class INSET:java.awt.Insets(top=3D0,bottom=3D0,left=3D0,right=3D0) loading gtkpeer init TRYING TO GET INTO GTKMAIN ACQUIRED LOCK TO RUN GTKMAIN 262 sablevm: INTERNAL ERROR (source file "native_interface.c", line 24655): todo [and commandline returned w/o any effect] XXXXXXX Test.class loading gtkpeer init TRYING TO GET INTO GTKMAIN ACQUIRED LOCK TO RUN GTKMAIN [and it seemed to eat 100% CPU here while hanging] I am attaching both (source) files used for testing. AFAIR they were in GNU ClassPath CVS repository, but were removed from there. Toby - do you have ANY (even trivial) Java app using AWT that runs w/ SableVM after applying your patch? Could you send it please? I would upload new 1.0.4 w/ your patch if I knew that it really helps to get anything really working. Best regards Grzegorz B. Prokopski PS: Etienne - please treat it as a bugreport (or feature request?) (I mean that INTERNAL ERROR above). You were saying you work on filling the holes in JNI interface, so maybe it's already fixed in your current version? |