seg fault on startup

Mon Mar 19 17:57:00 GMT 2007

 From the shared library version:
Core was generated by `/mnt/ide/Foo.shared.debug'.
Program terminated with signal 11, Segmentation fault.
#0 java.lang.NullPointerException.NullPointerException() (this=@300763f0)
 at 
/disk1/xtool/crosstool-0.43/build/powerpc-860-linux-gnu/gcc-4.1.2-glibc-2.3.3/gcc-4.1.2/libjava/classpath/java/lang/NullPointerException.java:70
70 
/disk1/xtool/crosstool-0.43/build/powerpc-860-linux-gnu/gcc-4.1.2-glibc-2.3.3/gcc-4.1.2/libjava/classpath/java/lang/NullPointerException.java: 
No such file or directory.
 in 
/disk1/xtool/crosstool-0.43/build/powerpc-860-linux-gnu/gcc-4.1.2-glibc-2.3.3/gcc-4.1.2/libjava/classpath/java/lang/NullPointerException.java
(gdb) bt
#0 java.lang.NullPointerException.NullPointerException() (this=@300763f0)
 at 
/disk1/xtool/crosstool-0.43/build/powerpc-860-linux-gnu/gcc-4.1.2-glibc-2.3.3/gcc-4.1.2/libjava/classpath/java/lang/NullPointerException.java:70
#1 0x0f1e6874 in catch_segv (_sc=@7fc00570) at 
/disk1/xtool/crosstool-0.43/build/powerpc-860-linux-gnu/gcc-4.1.2-glibc-2.3.3/gcc-4.1.2/libjava/prims.cc:151
#2 0x7fc00758 in ?? ()
#3 0x0f1e686c in catch_segv (_sc=@7fc00570) at 
/disk1/xtool/crosstool-0.43/build/powerpc-860-linux-gnu/gcc-4.1.2-glibc-2.3.3/gcc-4.1.2/libjava/prims.cc:151
#4 0x7fc00d18 in ?? ()
#5 0x0f1e686c in catch_segv (_sc=@7fc00570) at 
/disk1/xtool/crosstool-0.43/build/powerpc-860-linux-gnu/gcc-4.1.2-glibc-2.3.3/gcc-4.1.2/libjava/prims.cc:151
and on forever...perhaps an infinite loop?
-Ben
Andrew Haley wrote:
> Ben Tatham writes:
> > I'll respond directly to you for a moment, b/c i think this is outside 
> > the scope of the list...
> > 
> > btw...thank you SO much for all your incredibly quick help...
> > 
> > - I have a core dump from my target (ppc) platform, from running the 
> > debug version of libgcj and the app.
> > - When I open it with the target-specific gdb on our build server 
> > (namely powerpc-860-linux-gnu-gdb), I get the output listing below. As 
> > best I can tell, it is using the local versions of libgcc, libgcj, 
> > etc...not the powerpc versions. I am unclear as to how to get gdb to 
> > use the appropriate lib files to load the appropriate symbols...
>> Me either. If I were you I'd just make a few symlinks to the target
> libraries for gdb's benefit.
>> Andrew.
>