Re: Bug#525071: 2.2.4-1+b1 automatically rebuilt against libcrypto++8 segfaults on start
> I’m CC'ing debian-user in case there are people with i386/unstable/amule
> who can confirm or deny the segfault. Please CC firstname.lastname@example.org
> if you do so.
> Also, do you get any kind of backtrace, or can obtain one?
I can confirm this one, it crashes with a SIGSEGV.
Happens with the daemon as well as the UI.
Running unstable, i386:
$ gdb amuled
GNU gdb 6.8-debian
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb77ce6d0 (LWP 18004)]
0x24938a6c in ?? ()
#0 0x24938a6c in ?? ()
#1 0x7b299b74 in ?? ()
#2 0x00001220 in ?? ()
#3 0xb7eb6836 in CryptoPP::IteratedHashBase<unsigned int,
() from /usr/lib/libcrypto++.so.8
#4 0xb7ee5c88 in CryptoPP::RandomPool::IncorporateEntropy () from
#5 0xb7ed94ba in CryptoPP::AutoSeededRandomPool::Reseed () from
#6 0x081b1e1c in ?? ()
#7 0x081d108d in ?? ()
#8 0x0806bf00 in std::locale::locale ()
#9 0x0823c3f4 in ?? ()
#10 0xbf952648 in ?? ()
#11 0x080696bc in _init ()
Backtrace stopped: frame did not save the PC