aMule Forum

English => Backtraces => Topic started by: macias on October 02, 2006, 11:33:36 AM

Title: crash... (longer)
Post by: macias on October 02, 2006, 11:33:36 AM

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1093179872 (LWP 9263)]
0x0a930d78 in ?? ()
(gdb) #0  0x0a930d78 in ?? ()
#1  0x0000000c in ?? ()
#2  0x40bf96be in gdk_get_show_events () from /opt/gnome/lib/libgdk-x11-2.0.so.0
#3  0x0a930d68 in ?? ()
#4  0x00000205 in ?? () at formatter.h:190
#5  0x00000002 in ?? ()
#6  0x439029f0 in ?? ()
#7  0x40bf9660 in gdk_get_show_events () from /opt/gnome/lib/libgdk-x11-2.0.so.0
#8  0xbf919988 in ?? ()
#9  0x40fc215f in g_vasprintf () from /opt/gnome/lib/libglib-2.0.so.0
Previous frame inner to this frame (corrupt stack?)
(gdb) #0  0x0a930d78 in ?? ()
No symbol table info available.
#1  0x0000000c in ?? ()
No symbol table info available.
#2  0x40bf96be in gdk_get_show_events () from /opt/gnome/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#3  0x0a930d68 in ?? ()
No symbol table info available.
#4  0x00000205 in ?? () at formatter.h:190
        s_RunAtStartupSetPentiumFunctionPointers = 0 '\0'
        __ioinit = {static _S_refcount = , static _S_synced_with_stdio = }
        s_pSub = 0x82d4b22
        s_pAdd = 0x82d4ada
        s_vec = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"
        s_RunAtStartup = 0 '\0'
        RoundupSizeTable = {2, 2, 2, 4, 4, 8, 8, 8, 8}
        CryptoPP::Singleton, 0>::Ref(...) const::s_pObject = {m_p = 0xa065d28}
        CryptoPP::Singleton, 0>::Ref(...) const::s_objectState = 2 '\002'
        CryptoPP::Singleton, 0>::Ref(...) const::s_pObject = {
  m_p = 0xa368fc8}
---Type to continue, or q to quit---  CryptoPP::Singleton, 0>::Ref(...) const::s_objectState = 2 '\002'
        CryptoPP::cryptopp_assert_154 = {}
        CryptoPP::cryptopp_assert_155 = {}
        CryptoPP::cryptopp_assert_156 = {}
        CryptoPP::cryptopp_assert_158 = {}
        CryptoPP::cryptopp_assert_161 = {}
        CryptoPP::Singleton, 0>::Ref(...) const::s_pObject = {m_p = 0x0}
        CryptoPP::Singleton, 0>::Ref(...) const::s_objectState = 0 '\0'
        CryptoPP::PKCS_DigestDecoration::decoration = 0x8417364 "0!0\t\006\005+\016\003\002\032\005"
        CryptoPP::BufferedTransformation::NULL_CHANNEL = {static npos = 4294967295,
  _M_dataplus = {> = {<__gnu_cxx::new_allocator> = {}, },
    _M_p = 0x40793d5c ""}}
        CryptoPP::PKCS_DigestDecoration::length = 15
        CryptoPP::Singleton<__gnu_debug_def::vector >, CryptoPP::NewPrimeTable, 0>::Ref(...) const::s_pObject = {m_p = 0x0}
        CryptoPP::Singleton<__gnu_debug_def::vector >, CryptoPP::NewPrimeTable, 0>::Ref(...) const::s_objectState = 0 '\0'
        CryptoPP::g_nullNameValuePairs = { = {
    _vptr.NameValuePairs = 0x83bcb58}, }
        CryptoPP::AssignIntToInteger = (bool (*)(const struct std::type_info &, void *,
    const void *)) 0x82e3758
        CryptoPP::Singleton::Ref(...) const::s_pObject = {
  m_p = 0x0}
        CryptoPP::Singleton::Ref(...) const::s_objectState = 0 '\0'
#5  0x00000002 in ?? ()
No symbol table info available.
#6  0x439029f0 in ?? ()
No symbol table info available.
#7  0x40bf9660 in gdk_get_show_events () from /opt/gnome/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#8  0xbf919988 in ?? ()
No symbol table info available.
#9  0x40fc215f in g_vasprintf () from /opt/gnome/lib/libglib-2.0.so.0
No symbol table info available.

Title: Re: crash... (longer)
Post by: phoenix on October 18, 2006, 03:00:40 PM

macias,

Your problem seems related to the cryptoPP llibrary you are using. Are you using our version or a system installed version? I would advise to use the one in aMule code, which should be the default if you are compiling yourself.

Cheers!

Title: Re: crash... (longer)
Post by: macias on October 18, 2006, 07:43:13 PM

Quote

Originally posted by phoenix
macias,

I would advise to use the one in aMule code, which should be the default if you are compiling yourself.

Cheers!

I compiled it (amule) by myself. How to check it for sure?

Title: Re: crash... (longer)
Post by: Gerd78 on October 19, 2006, 06:15:51 PM

If you still have the config.log file from that custom build, it's documented there. You can attach that file for reference.

But I'm pretty sure that you're using the aMule internal code. aMule always uses the internal CryptoPP code unless explicitly told not to.

Title: Re: crash... (longer)
Post by: macias on October 19, 2006, 07:25:10 PM

I deleted the .log file as well the whole build dir. I didn't set anything special with configure, --enable-shared --enable-debug and that pretty much all.

Title: Re: crash... (longer)
Post by: phoenix on October 20, 2006, 02:04:22 AM

Quote

#3 0x0a930d68 in ?? ()
No symbol table info available.
#4 0x00000205 in ?? () at formatter.h:190
s_RunAtStartupSetPentiumFunctionPointers = 0 '\0'

Well, I see a lot of pointers inside system libraries, your backtrace is probably trash. There is no source file "formatter.h" in aMule or wxWidgets code. I don't know where did gdb got this debug information from. Is that something that happens a lot? In my experience, compiling aMule AND wxWidgets from source has always fixed my crash problems like this one.

Cheers!

Title: Re: crash... (longer)
Post by: macias on October 20, 2006, 07:56:47 AM

When the package is already done, I use it, otherwise I compile it from the sources. So now, I have aMule compiled by myself, and wxGTK built by someone else (from package).

Crashes are not often in aMule I would say, but I don't remember occurrences of each particular.

Ok, I will try to compile wxGTK by myself too.