Re: [Sablevm-developer] Partial success w/ debbuggtk - screenshot!

[David <db...@cs...>]

On Tue, Jan 20, 2004 at 01:19:03AM -0500, Grzegorz B. Prokopski wrote:
> Hi all!
>=20
> I copied AllocObject and DeleteGlobalRef from David's sandbox [*] and
> was able to get "bugreporter" utility that far (thanks David!):
> http://gadek.homelinux.org/debbuggtk-sablevm.png
>=20
> This error shows up, but the app continues in spite of it:
> $ bugreporter=20
> *** Couldn't bind native method Java_java_lang_VMThread_interrupted ***
> *** or Java_java_lang_VMThread_interrupted__ ***
> Exception in thread "Lazy cache writer" java.lang.UnsatisfiedLinkError
>    at java.lang.VMThread.interrupted (VMThread.java)
>    at java.lang.Thread.interrupted (Thread.java:572)
>    at com.tildemh.debbug.CacheWriter.run (CacheWriter.java:45)
>    at java.lang.Thread.run (Thread.java:455)
>    at java.lang.VMThread.callRun (VMThread.java:116)
>    at java.lang.Thread.callRun (Thread.java:333)
>    at java.lang.VirtualMachine.runThread (VirtualMachine.java:117)
>=20
> This one is SableVM/Classpath problem, no? How hard would it be
> to fix it?

You will probably need to ask Etienne to implement it...

This requires implementing the Thread interrupt()ing mechanism in
SableVM.  If I remember well there is no functionality right now.
In addition to Thread.interrupted(), .interrupt(), etc.
Object.wait(), Process.waitFor(), maybe also join() and sleep()...
need to be modified to throw InterruptedException.

So, it is not simply playing with VM/Classpath interface...


>=20
> I can go to the next screen by pressing Forward, I can put package
> name into edit window, however after next Forward it dies with:
> (Gtk.java:-1)  org/gnu/gtk/Gtk.gtk_main  n
> (Gtk.java:64)  org/gnu/gtk/Gtk.main  =20
> (BugReporter.java:257)  com/tildemh/debbuggtk/BugReporter.main  =20
> (VirtualMachine.java:-1)  java/lang/VirtualMachine.invokeMain  n
> (VirtualMachine.java:88)  java/lang/VirtualMachine.main  =20
> [jni: fatal error (Local reference capacity exceeded)]
>=20
> Which in this case seems to be again problem of gtk-java libs
> not freeing (leaking) references.

Yes, basically it would need to be fixed in the code that allocates
them.

> Anyway, I am very happy, because it is first real graphical window
> that I was able to see using SableVM on my machine.
>=20

Bravo!

Your app seem to be good to test JNI and other stuff.


>=20
> [*] I guess then that as AllocObject and DeleteGlobalRef have been
> excersised, they're good enough to go into staging.=20
>=20

they were simple...


David

---

David B=E9langer
Graduate Student
School of Computer Science
McGill University
Office: MC226

Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt