Error messages

Fri Oct 12 04:52:00 GMT 2001

Torsten RÃƒÂ¼ger writes:
 > as a newbie, I keep making silly mistakes. These usually end in "core 
 > dumped", which to me is not very informative. (Especially being used to 
 > Java stack traces)
gcj gives you a Java stack trace. If it doesn't there's an
installation problem.
 > So I get the debuger out and look. Below are some stack traces:
 > 1 - I think was because by linking in one of those object files where 
 > the class has a $ at the end. So that would be an UnresolvedClassError
 > 2 - ?? anyone has a clue ?
 > 
 > 1 --
 > Starting program: /tmp/platform/Main
 > [New Thread 1024 (LWP 4228)]
 > 
 > Program received signal SIGABRT, Aborted.
 > [Switching to Thread 1024 (LWP 4228)]
 > 0x4051c801 in __kill () from /lib/i686/libc.so.6
 > (gdb) where
 > #0 0x4051c801 in __kill () from /lib/i686/libc.so.6
 > #1 0x404cf61b in raise (sig=6) at signals.c:65
 > #2 0x4051dd82 in abort () at ../sysdeps/generic/abort.c:88
It looks like an attempt to throw an exception has failed because the
exception unwinder hasn't found the unwind info that it needs. This
points to some sort of installation problem.
However, the cause of the second problem might be related to a recent
problem that we already know about where the Boehm garbage collector
is being miscompiled.
Please, we need to know exactly what your OS is and what your relase
of gcj is. Please note that you can't mix different versions of gcj,
gcc, and libgcj: they must be compiled from the same source tree.
Use the command 'ldd' on your executable so that we can find the
libraries you're linking with.
Andrew.