Core dump (Illegal instruction) with crosstool's GCJ

Martin Egholm Nielsen
Thu Jun 17 10:17:00 GMT 2004

Hi Dan,

>> Until recently I only had problems when I trying to compile any small 
>> Java-source with "-static". Applications linked like that wouldn't 
>> execute on the target and would cause a core dump immediately after 
>> start (signal 4, Illegal instruction).
>> However, now I've have a small test-example (dynamically linked) using 
>> the java.lang.reflect.Proxy-class, that'll fail consequently (Illegal 
>> instruction) performing some specific Java-action.
>> The crosscompiler has been build on cygwin with crosstool-0.28-rc13 
>> with the for the ppc405-target with gcc-3.4.0-glibc-2.2.5.dat.
>> A similar compiler has been created under my RedHat, and also a 
>> cygwin-compiler with glibc-2.3.2.
>> The target system runs the a root-filesystem from ELDK 2.0.2 (or maybe 
>> 2.2.0) from Denx Software, and the kernel is a patched 2.4.20 from 
>> DAVE ( specific for my PPChameleonEVB-board.
Now, I've tried using the root-filesystem from ELDK 3.0 which uses 
glibc-2.3.1 and gcc-3.2.2, and with my crosstool-cygwin-3.4.0-2.3.2 I 
_can_ now use static builds of _sample_ programs - not my faulty 
application (of course) (but this is still something I couldn't do before).
But I still cannot run a static application linked with 
That made me wonder: What are the requirements between compiler- and 
glibc-versions for crosstool-compiled applications and the 
target-system's system (both kernel and shell(?))?
Do I need to compile an entire root-filesystem with the exact same 
crosscompiler as my gcj-applications are compiled with?

I hope this makes any sense to you - I too am a bit confused :o)

Best regards,

Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list