> This is the output of ./crypto/bn/divtest.c after some minutes of running:
>
> d:\net\openssl.095\bin>divtest.exe
> BN_div_recp failed!
> a=21CC27865629353755638C3726DF4C2D1C976729D1CD3C3FFC01039CE01B6687959E2BB84BAB54
> D798D9873CAED7007AB955B025F799BDE5AE4C84D79DE7B35E7ED2A43
> b=1
> BN_div_recp failed!
> a=7F20C2B8FFD1935CA0C8D43CA4373F4FD113CF7A6EE00FAC2FDA807C2D56A4EDD006B252EF4814
> F78D403A2B908D284C15096CDA0EFD9D0AA2F272E1CC6D2BB56604367BC10657B63F5
> b=4
> BN_div_recp failed!
> a=1B06C262E40A4CC742ED24FEDD52FEB8051BD3B37CFDF5CD1F2EE90E5F3C88A9C6D9FD1C931FD5
> C19AB65D85224D75D056EB2EAF421EB996EB6730168F39FDB11A0C16569CADFF14244FD
> b=8
>
> Target is DOS + djgpp 2.03, gcc 2.95.2 + Perl 5.004.
I can't reproduce the problem with gcc 2.95.2 on Linux...
> More flags:
>
> d:\net\openssl.095\bin>openssl.exe version -a
> OpenSSL 0.9.5beta2-dev 28 Feb 2000
> built on: Feb 28 2000
> platform: DOS (djgpp)
^^^^^^^^^^^ Well, we don't have such target in config
scripts. Is it something you've "cooked" yourself? Can you disclose the
line then?
> options: bn(32,32)
^^ Yes, I've tried this as well...
> -DBN_DEBUG
^^^^^^^^^ But I wonder how did you get through the compilation? There
is a typo in crypto/bn/bn_asm.c in 0.9.5beta2 triggered by -DBN_DEBUG.
If you've never discovered the typo, then it means only one thing, you
link with assembler module... Which assumes bn(64,32) option... Well,
shouldn't really matter... At least I can't imagine it would... But can
you reproduce the problem if you compile the toolkit with BN_LLONG? And
post the whole config line:-)
Andy.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
