aMule Forum

English => Backtraces => Topic started by: myth on May 10, 2009, 06:05:27 PM

Title: Crash sending message
Post by: myth on May 10, 2009, 06:05:27 PM

I just uploaded an file to stu redman for testing purpose...after transfer finished, i wanted to send him a message, and crash!

Code: [Select]

ASSERT INFO:
../../src/ChatSelector.cpp(248): assert "wxAssertFailure" failed in SendMessage().

BACKTRACE:
[1] CChatSelector::SendMessage(wxString const&, wxString const&, unsigned long long) /build/buildd/amule-2.3.0~svnr9596/obj-i486-linux-gnu/src/../../src/ChatSelector.cpp:248
[2] CChatWnd::SendMessage(wxString const&, wxString const&, unsigned long long) /build/buildd/amule-2.3.0~svnr9596/obj-i486-linux-gnu/src/../../src/ChatWnd.cpp:148
[3] CChatWnd::OnBnClickedCsend(wxCommandEvent&) /build/buildd/amule-2.3.0~svnr9596/obj-i486-linux-gnu/src/../../src/ChatWnd.cpp:74
[4] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) cons)
[5] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[6] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[7] wxEvtHandler::ProcessEvent(wxEvent&)
[8] wxWindowBase::TryParent(wxEvent&)
[9] wxEvtHandler::ProcessEvent(wxEvent&)
[10] wxTextCtrl::OnChar(wxKeyEvent&)
[11] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) cons)
[12] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[13] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[14] wxEvtHandler::ProcessEvent(wxEvent&)
[15] g_closure_invoke()
[16] g_signal_emit_valist()
[17] g_signal_emit()
[18] gtk_window_propagate_key_event()
[19] g_closure_invoke()
[20] g_signal_emit_valist()
[21] g_signal_emit()
[22] gtk_propagate_event()
[23] gtk_main_do_event()
[24] g_main_context_dispatch()
[25] g_main_loop_run()
[26] gtk_main()
[27] wxEventLoop::Run()
[28] wxAppBase::MainLoop()

Title: Re: Crash sending message
Post by: Stu Redman on May 10, 2009, 10:05:34 PM

That's not a crash - it's a debug assertion. A controlled exception in debug builds if unexpected things happen.

What happened here: you sent a corruped block and my client banned and disconnected you. Because of my disconnect my client disappeared in your client list too, which was unexpected by the chat session at this point.

I'll look into it.

Title: Re: Crash sending message
Post by: Stu Redman on May 11, 2009, 10:30:40 PM

Fixed in 9602.