[Bug 189243] Re: please sync libcrypto++ 5.5.2-1 from Debian testing

Zooko O'Whielacronx zooko at zooko.com
Tue Feb 5 20:48:17 GMT 2008


On Feb 5, 2008, at 1:28 PM, Nicolas Valcárcel (nxvl) wrote:

> Ok, it builds fine, but it crashes on use, here is the output of the
> error.

Thanks for working on this.

Did you figure out that aMule was not linking to libcryptopp at all,  
and it is aMule using its own internal copy of CryptoPP that crashes,  
or is it linking to the new v5.5.2 of libcryptopp that crashes?  Or  
is it linking to the old v5.5 of libcryptopp that crashes?

more comments below:

> ----------------------------=| BACKTRACE FOLLOWS: | 
> =----------------------------
> Current version is: aMule 2.1.3 using wxGTK2 v2.8.6 (Unicoded)
> Running on: Linux 2.6.24-5-generic i686
>
> [2] wxThreadHelperThread::~wxThreadHelperThread() in amule [0x808311b]
> [3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.8.so.0[0xb75d3446]
> [4] ?? in [0xb7f36420]
> [5] wxGIFDecoder::GetFrameSize(unsigned int) const in /usr/lib/ 
> libwx_gtk2u_core-2.8.so.0[0xb7894df2]
> [6] wxGIFDecoder::ConvertToImage(unsigned int, wxImage*) const in / 
> usr/lib/libwx_gtk2u_core-2.8.so.0[0xb7894e5c]
> [7] wxTextCtrl::wxTextCtrl() in amule [0x82339cd]
> [8] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*) 
> (wxEvent&), wxEvent&) const in /usr/lib/libwx_baseu-2.8.so.0 
> [0xb7527341]
> [9] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase  
> const&, wxEvtHandler*, wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0 
> [0xb75cedf8]
> [10] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/ 
> lib/libwx_baseu-2.8.so.0[0xb75cef58]
> [11] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib/ 
> libwx_baseu-2.8.so.0[0xb75cf0bf]
> [12] wxTimerBase::Notify() in /usr/lib/libwx_gtk2u_core-2.8.so.0 
> [0xb78e03e1]
> [13] ?? in /usr/lib/libwx_gtk2u_core-2.8.so.0 [0xb77bc535]
> [14] ?? in /usr/lib/libglib-2.0.so.0 [0xb6f544e6]
> [15] g_main_context_dispatch in /usr/lib/libglib-2.0.so.0[0xb6f53d76]
> [16] ?? in /usr/lib/libglib-2.0.so.0 [0xb6f57133]
> [17] g_main_loop_run in /usr/lib/libglib-2.0.so.0[0xb6f57517]
> [18] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0xb6ce2d94]
> [19] wxEventLoop::Run() in /usr/lib/libwx_gtk2u_core-2.8.so.0 
> [0xb77b2fec]
> [20] wxAppBase::MainLoop() in /usr/lib/libwx_gtk2u_core-2.8.so.0 
> [0xb7854cee]
> [21] wxAppBase::OnRun() in /usr/lib/libwx_gtk2u_core-2.8.so.0 
> [0xb7854341]
> [22] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.8.so.0 
> [0xb75632ea]
> [23] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.8.so.0 
> [0xb7563397]
> [24] CryptoPP::IteratedHash<unsigned int,  
> CryptoPP::EnumToType<CryptoPP::ByteOrder, 0>, 64u,  
> CryptoPP::HashTransformation>::~IteratedHash() in amule [0x812b3d0]
> [25] __libc_start_main in /lib/tls/i686/cmov/libc.so.6[0xb727e450]
> [26] wxNotebook::SetPadding(wxSize const&) in amule[0x807f451]

This is a pretty weird stack trace -- the destructor of a CryptoPP  
IteratedHash object calls __libc_start_main(), which then calls  
wxNotebook::SetPadding()?

Anyway, a crash in a destructor like this makes me suspect a memory  
management bug in aMule.  Could you please run it with valgrind?

Regards,

Zooko

-- 
please sync libcrypto++ 5.5.2-1 from Debian testing
https://bugs.launchpad.net/bugs/189243
You received this bug notification because you are a member of Ubuntu
Sponsors for universe, which is a direct subscriber.



More information about the Ubuntu-universe-sponsors mailing list