[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bouncycastle-crypto-dev
Subject:    Re: [dev-crypto] Illegal instruction when loading BouncyCastle under
From:       Martin Morissette <mmorissette () 8d ! com>
Date:       2009-01-27 15:19:32
Message-ID: 497F2604.2030406 () 8d ! com
[Download RAW message or body]

It turns out, the SIGILL was caused by my build of CVM. By disabling the
use of hardware floating point in the VM's JIT, it all works fine!

I'm guessing I was only having this issue when the bouncy castle jars
where on the classpath because they are signed.

Martin

Martin Morissette wrote:
> Hi all,
> 
> I am trying to use BouncyCastle under a latest SVN build of phoneME
> (cvm) with the CDC Foundation profile. Whenever I add
> bcprov-jdk14-141.jar to the classpath, phoneME (cvm) crashes with a
> SIGILL Illegal Instruction error. Since the opensource version of cvm,
> phoneME, does not come with the Security Optional packages, I am using
> JCE 1.2.2 that I found on a Sun Archives site.
> 
> So, to run my app, I use the following command:
> phoneme/usr/local/bin/cvm -cp
> phoneme/usr/local/lib/US_export_policy.jar:phoneme/usr/local/lib/foundation.jar:phon \
> eme/usr/local/lib/jce1_2_2.jar:phoneme/usr/local/lib/local_policy.jar:phoneme/usr/lo \
> cal/lib/sunjce_provider.jar:c9es/jar/bcprov-jdk14-141.jar:c9es/jar/bipa.jar:c9es/jar \
> /c9oe.jar:c9es/jar/commons-beanutils-core-1.8.0.jar:c9es/jar/commons-logging-api-1.1 \
> .jar:c9es/jar/commons-net-1.4.1.jar:c9es/jar/dtk.jar:c9es/jar/g3.jar:c9es/jar/glue.jar:c9es/jar/ntk.jar:c9es/jar/shell.jar:
>  com.eightd.ntk.test.BouncyCastle
> 
> And the result, when ran in GDB, is:
> 
> [Thread debugging using libthread_db enabled]
> [New Thread 0x4001eff0 (LWP 6446)]
> [New Thread 0x41073490 (LWP 6449)]
> [New Thread 0x41873490 (LWP 6450)]
> 
> Program received signal SIGILL, Illegal instruction.
> [Switching to Thread 0x4001eff0 (LWP 6446)]
> 0x4019d574 in ?? ()
> 
> I have not yet managed to build phoneME with proper debugging info
> enabled. Nonetheless, does anyone have any idea what the issue might be?
> 
> Regards,
> Martin
> 
> 
> 


[prev in list] [next in list] [prev in thread] [next in thread]