run "make tests" in the OpenSSL build tree, or even "openssl speed rsa".
That'll test the code paths with known good code.
If it doesn't hang it's a problem in your code somewhere (try running under
valgrind at that point)- if it does hang , you should get better
diagnostics from make tests.
Peter
From: Brendan Plougonven <[email protected]>
To: "[email protected]" <[email protected]>
Date: 01/09/2010 01:42 AM
Subject: bn_mul_add_words() hangs on my linux-x86_64 built
Sent by: [email protected]
I built an application that includes omniORB which statically links to
openssl-0.9.8k and it hangs with the following stack:
#0 0x0000002aa7774419 in bn_mul_add_words ()
#1 0x0000002aa77bdd5c in BN_from_montgomery ()
#2 0x0000002aa77bdb7b in BN_mod_mul_montgomery ()
#3 0x0000002aa77b63c0 in BN_mod_exp_mont ()
#4 0x0000002aa77bc93e in witness ()
#5 0x0000002aa77bc880 in BN_is_prime_fasttest_ex ()
#6 0x0000002aa77bc324 in BN_generate_prime_ex ()
#7 0x0000002aa78ca089 in rsa_builtin_keygen ()
#8 0x0000002aa78c9e20 in RSA_generate_key_ex ()
#9 0x0000002aa78c05fa in RSA_generate_key ()
#10 0x0000002aa78b9944 in sslContext::set_ephemeralRSA ()
#11 0x0000002aa78ba06f in sslContext::internal_initialise ()
#12 0x0000002aa78b92af in omni::omni_sslTransport_initialiser::attach ()
#13 0x0000002aa780542c in omni::omni_hooked_initialiser::attach ()
#14 0x0000002aa7802adb in CORBA::ORB_init ()
#15 0x0000002aa76f4926 in CORBAorb::initialize ()
That looks like the issue 11. In the [BUILD] section of the FAQ.
./config –t and openssl version –p give the same value linux-x86_64
I built openssl with:
./Configure shared no-rc5 no-idea enable-fips no-asm no-sse2 linux-x86_64
--prefix=`pwd`
I tried ./config shared, but that led to the same results.
It was built on Red Hat Enterprise Linux AS release 4 (Nahant Update 8).
Linux 2.6.9-67.0.7.EL #1 Wed Feb 27 04:37:13 EST 2008 x86_64 x86_64 x86_64
GNU/Linux
with gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-11)
Would anyone have a clue as to what is wrong with my build ?
Brendan
