Bug 75257 – xmule 1.9.4b crashed after creatiing Cryptkey.dat

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Marcin Kurek 2004-12-21 16:47:08 UTC]

xmule crashed after fresh emerge.

Reproducible: Always
Steps to Reproduce:
1. Run xmule executable
2.
3.

Actual Results:  
After the 'Creating new Cryptkey.dat ... 41c8c263 41c8c263' message (This takes 
realy loong time here) xmule exits with following errorr message

xmule: CryptoXMpp.cpp:3913: void CryptoXMpp::CorrectQuotientEstimate(CryptoXMpp:
:word*, CryptoXMpp::word*, CryptoXMpp::word*, const CryptoXMpp::word*, unsigned 
int): Assertion `!borrow && !R[N + 1]' failed.
Aborted



xmule USE='-debug +gtk2 +nls'

[Comment 1 Raphael Slinckx 2004-12-23 12:53:45 UTC]

Nearly the same for me !
---------------------------
Initialising xMule
Setting value of secure-ident to true.
Setting value of source-exchange to true.
Setting value of command-line to true.
*** UDP socket at 4672
Creating new Cryptkey.dat ... 41cb329f 41cb329f
xmule: CryptoXMpp.cpp:3629: void CryptoXMpp::RecursiveMultiplyTop(CryptoXMpp::word*, CryptoXMpp::word*, const CryptoXMpp::word*, const CryptoXMpp::word*, const CryptoXMpp::word*, unsigned int, const P*) [with P = CryptoXMpp::LowLevel]: Assertion `carry >= 0 && carry <= 2' failed.
zsh: abort      xmule
------------------------

[Comment 2 HopeSeekr 2005-01-03 18:42:05 UTC]

This is due to compilation.  Because of the new extended usage of Crypto++ inorder to support 64bit and PowerPC platforms (or really any platform that Crypto++ supports) these problems have surfaced in recent versions of xMule.

To get rid of it, CryptoXMpp.cpp of xMule *must* be compiled with *NO* optimizations...Zero, zip, nada.  It's already highly-optimized code and GCC just borks it.

I also editing some ASM around v1.9.2 and that *may* have to do it, tho I was told the symbol "ebp" that was removed does little on modern machines and is only usable on i686's (not even i586s).

In all future versions of xMule, it would be nice if gentoo maintainers either enforced 0 optimization of CryptoXMpp.cpp (I will probably do this for you via specialized Makefile :p) or (preferably) link xMule to libcrypto++ if available.

Hope of xMule

[Comment 3 Raphael Slinckx 2005-01-04 03:07:37 UTC]

Right, it worked after setting more conservative CFLAGS..

[Comment 4 Michael Hanselmann (hansmi) (RETIRED) 2005-01-28 11:34:32 UTC]

I think that it would be cleaner to link against libcrypto++. Handing over to net-p2p for this.

[Comment 5 HopeSeekr 2005-03-14 10:39:31 UTC]

This has been fixed in 1.9.5..

[Comment 6 Ioannis Aslanidis (RETIRED) 2005-03-22 05:50:30 UTC]

Same error on amd64 with version 1.9.4b

[Comment 7 Karol Wojtaszek (RETIRED) 2005-03-22 14:07:40 UTC]

*** Bug 73325 has been marked as a duplicate of this bug. ***

[Comment 8 Karol Wojtaszek (RETIRED) 2005-03-22 14:08:33 UTC]

xmule-0.10.0 added to portage.