the gentoo bug squashers have marked the crypto++ problem fixed but it's obviously not.
re-emerged current gentoo crypto++-5.6.0-r1 and amule 2.2.6
gdb /usr/bin/amule
warning: Can not parse XML syscalls information; XML support was disabled at compile time.
GNU gdb (Gentoo 7.0 p1) 7.0
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/amule...Reading symbols from /usr/lib/debug/usr/bin/amule.debug...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/amule
[Thread debugging using libthread_db enabled]
^C
Program received signal SIGINT, Interrupt.
0xb7d99a31 in CryptoPP::X86_SHA256_HashBlocks(unsigned int*, unsigned int const*, unsigned int) () from /usr/lib/libcrypto++.so.0
(gdb) bt
#0 0xb7d99a31 in CryptoPP::X86_SHA256_HashBlocks(unsigned int*, unsigned int const*, unsigned int) () from /usr/lib/libcrypto++.so.0
Cannot access memory at address 0x9cfec676
(gdb) bt full
#0 0xb7d99a31 in CryptoPP::X86_SHA256_HashBlocks(unsigned int*, unsigned int const*, unsigned int) () from /usr/lib/libcrypto++.so.0
No symbol table info available.
Cannot access memory at address 0x9cfec676
(gdb) thread apply all bt
Thread 1 (Thread 0xb4ee4720 (LWP 6714)):
#0 0xb7d99a31 in CryptoPP::X86_SHA256_HashBlocks(unsigned int*, unsigned int const*, unsigned int) () from /usr/lib/libcrypto++.so.0
Cannot access memory at address 0x9cfec676
(gdb) kill
Kill the program being debugged? (y or n) y
(gdb)