Re: need hints on debugging both classpath and jamvm to run ImageJ

[Andreas Tobler]

Albert Cardona wrote:

> So now: what is the best way to debug both classpath and jamvm ? When running 
> jamvm from ddd, I get:
>
> Using host libthread_db library "/lib/libthread_db.so.1".
> (gdb) 
> run -Xbootclasspath/a:/home/albertca/Programming/jamvm/jamvm-local/share/classpath/glibj.zip:/home/albertca/Programming/jamvm/jamvm-local/share/classpath/tools.zip:/home/albertca/Programming/jamvm/jamvm-local/share/classpath -Dgnu.classpath.boot.library.path=/home/albertca/Programming/jamvm/jamvm-local/lib/classpath -Xmx384Mb -classpath ./ij.jar:./jars/colt.jar:./jars/jai_imageio.jar:./jars/jimi.jar:./jars/jpedal/additional_jars/bcprov-jdk14-119.jar:./jars/jpedal/additional_jars/jdom.jar:./jars/jpedal/pjes.jar:./jars/jpedal/14_os_jpedal.jar:./jars/jython21/jython.jar:./jars/postgresql-8.1-405.jdbc3.jar 
> ij.ImageJ
> [Thread debugging using libthread_db enabled]
> [New Thread 805413360 (LWP 7972)]
> [New Thread 1225315568 (LWP 7975)]
> [New Thread 1233704176 (LWP 7976)]
>
> Program received signal SIGUSR1, User defined signal 1.
> [Switching to Thread 805413360 (LWP 7972)]
> 0x0fe52f68 in clone () from /lib/libc.so.6
>
>
> Meaning, the program doesn't run at all! I can't see what is different than 
> running the program from the command line. Using a -classpath ij.jar only (no 
> extensions to ImageJ) results in exactly the same problem.
>
> How is one to debug GNU Classpath and/or jamvm? Or are the above GNU Classpath 
> problems only?

gdb :)

to pass the above SIGUSR1 you have to advise gdb how handle them.

(gdb) handle SIGUSR1 nostop

This advises gdb to continue when such a signal occurs.

You can do it for every signal, but here SIGUSR1|2 are useful only.

Now you can debug your real problem.

Hope it helps,

Andreas