aMule Forum

English => Backtraces => Topic started by: paddiloo on December 13, 2008, 12:59:42 PM

Title: aMuled 2.2.2 recurrently crashes on F10 i386
Post by: paddiloo on December 13, 2008, 12:59:42 PM

error log is in attachment.

I will try to collect the backtrace with debug information installed and will keep you posted.

Regards.
A

Title: Re: aMuled 2.2.2 recurrently crashes on F10 i386
Post by: paddiloo on December 13, 2008, 11:05:19 PM

Hi iz0bbz,

it is rpmfusion, indead. sorry for not mentioning it.

rpmfusion's amule debuginfo package was pretty useless so far. So, if it can help, I'll take the SVN version, no problem.

Title: Re: aMuled 2.2.2 recurrently crashes on F10 i386
Post by: paddiloo on December 14, 2008, 02:35:36 PM

Hi,

here's the follow up.

The SVN version crashes as well, see error-log below.

I will see if a core file can be generated for gdb backtrace generation but a debug-info package would help a lot, do you have it available?

A

--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    http://forum.amule.org/index.php?board=67.0
If possible, please try to generate a real backtrace of this crash:
    http://www.amule.org/wiki/index.php/Backtraces

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMuled SVN using wxGTK2 v2.8.9 (Snapshot: rev. 9251)
Running on: Linux 2.6.27.7-134.fc10.i686 i686

[2] ?? in /usr/bin/amuled [0x807b9f1]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.8.so.0[0x34bd26]
[4] ?? in [0x110400]
[5] ?? in /usr/bin/amuled [0x808b7b8]
[6] ?? in /usr/bin/amuled [0x80d4b7d]
[7] ?? in /usr/bin/amuled [0x808bb6e]
[8] ?? in /usr/bin/amuled [0x809afa8]
[9] ?? in /usr/bin/amuled [0x809d811]
[10] ?? in /usr/bin/amuled [0x807cc0c]
[11] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const in /usr/lib/libwx_baseu-2.8.so.0[0x2a5d91]
[12] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0[0x3471ba]
[13] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/lib/libwx_baseu-2.8.so.0[0x3483d4]
[14] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0[0x3484db]
[15] wxEvtHandler::ProcessPendingEvents() in /usr/lib/libwx_baseu-2.8.so.0[0x347639]
[16] wxAppConsole::ProcessPendingEvents() in /usr/lib/libwx_baseu-2.8.so.0[0x2a60f1]
[17] ?? in /usr/bin/amuled [0x8072615]
[18] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.8.so.0[0x2e0caa]
[19] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.8.so.0[0x2e0ea7]
[20] ?? in /usr/bin/amuled [0x8072940]
[21] __libc_start_main in /lib/libc.so.6[0x51e6d5]
[22] ?? in /usr/bin/amuled [0x8070661]

Title: Re: aMuled 2.2.2 recurrently crashes on F10 i386
Post by: paddiloo on December 14, 2008, 09:42:40 PM

Hi again,

my conf is in attachement, your link does not work much so far.

I will organize scp transfer instead if you don't mind (in your MP)

Cheers,
A 

Title: Re: aMuled 2.2.2 recurrently crashes on F10 i386
Post by: paddiloo on December 16, 2008, 12:45:36 AM

Hi,

thanks for the debuginfo and here are the final backtraces.

cheers,
A

Title: Re: aMuled 2.2.2 recurrently crashes on F10 i386
Post by: paddiloo on December 16, 2008, 08:55:39 AM

Hi again,

don't know if it can help but this is my core dump analysis.

* At frame 9, parameter str2 seems broken (probably a reference to NULL data)


(gdb) f 9
#9  operator+ (str1=@0xbfa4a270, str2=@0x918b418) at src/common/string.cpp:1151
1151       s += str2;
(gdb) p str1
$6 = (const wxString &) @0xbfa4a270: {<wxStringBase> = {
    static npos = 4294967295, m_pchData = 0x9e66804}, <No data fields>}
(gdb) p str2
$7 = (const wxString &) @0x918b418: {<wxStringBase> = {
    static npos = 4294967295, m_pchData = 0x20}, <No data fields>}


* str1 data seems ok (string: "Direct callback failed to client ")

(gdb) x/32wc 0x9e66804
0x9e66804:   68 'D'   105 'i'   114 'r'   101 'e'
0x9e66814:   99 'c'   116 't'   32 ' '   99 'c'
0x9e66824:   97 'a'   108 'l'   108 'l'   98 'b'
0x9e66834:   97 'a'   99 'c'   107 'k'   32 ' '
0x9e66844:   102 'f'   97 'a'   105 'i'   108 'l'
0x9e66854:   101 'e'   100 'd'   32 ' '   116 't'
0x9e66864:   111 'o'   32 ' '   99 'c'   108 'l'
0x9e66874:   105 'i'   101 'e'   110 'n'   116 't'

* str2 on the other hand is not

(gdb) x/32wc 0x20
0x20:   Cannot access memory at address 0x20

on frame 10 one can identify the str1.

1220         AddDebugLogLineM(false, logClient, wxT("Direct callback failed to client ") + GetUserHash().Encode() + wxT(" on ip ") + GetFullIP());

Conclusion:
===========

GetUserHash().Encode() returned a broken (NULL?) string.

Regards,
A