aMule Forum

English => en_Bugs => Topic started by: macias on April 03, 2011, 04:49:39 PM

Title: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: macias on April 03, 2011, 04:49:39 PM


At some point I get this message (when aMule is running):

Code: [Select]
ASSERT INFO:
EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().

BACKTRACE:
[1] wxOnAssert(wchar_t const*, int, char const*, wchar_t const*, wchar_t const*)
[2] CEncryptedStreamSocket::Negotiate(unsigned char const*, unsigned int) /home/user/rpm/BUILD/aMule-2.2.6/src/EncryptedStreamSocket.cpp:684
[3] CEncryptedStreamSocket::Read(void*, unsigned int) /home/user/rpm/BUILD/aMule-2.2.6/src/EncryptedStreamSocket.cpp:303
[4] CEMSocket::OnReceive(int) /home/user/rpm/BUILD/aMule-2.2.6/src/EMSocket.cpp:227
[5] CClientTCPSocket::OnReceive(int) /home/user/rpm/BUILD/aMule-2.2.6/src/ClientTCPSocket.cpp:1933
[6] CClientTCPSocketHandler::ClientTCPSocketHandler(wxSocketEvent&) /home/user/rpm/BUILD/aMule-2.2.6/src/ClientTCPSocket.cpp:96
[7] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) cons)
[8] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[9] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[10] wxEvtHandler::ProcessEvent(wxEvent&)
[11] wxEvtHandler::ProcessPendingEvents()
[12] wxAppConsole::ProcessPendingEvents()
[13] wxAppBase::ProcessIdle()
[14] g_main_context_dispatch()
[15] g_main_loop_run()
[16] gtk_main()
[17] wxEventLoop::Run()
[18] wxAppBase::MainLoop()
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: Stu Redman on April 03, 2011, 08:33:33 PM
No. Do NOT patch wx 2.8.12. It already has a different form of the patch included, applying the original patch to it again will be disastrous.
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: macias on April 04, 2011, 06:02:13 PM
I applied the patch because of your very post :-) (the one about solving the issue with handling high traffic).

Anyway, I removed the patch, packaged wxGTK again, and I get this assertion again. Just in case new stack trace:

Code: [Select]
ASSERT INFO:
EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().

BACKTRACE:
[1] wxOnAssert(wchar_t const*, int, char const*, wchar_t const*, wchar_t const*)
[2] CEncryptedStreamSocket::Negotiate(unsigned char const*, unsigned int) /home/user/rpm/BUILD/aMule-2.2.6/src/EncryptedStreamSocket.cpp:684
[3] CEncryptedStreamSocket::Read(void*, unsigned int) /home/user/rpm/BUILD/aMule-2.2.6/src/EncryptedStreamSocket.cpp:303
[4] CEMSocket::OnReceive(int) /home/user/rpm/BUILD/aMule-2.2.6/src/EMSocket.cpp:227
[5] CClientTCPSocket::OnReceive(int) /home/user/rpm/BUILD/aMule-2.2.6/src/ClientTCPSocket.cpp:1933
[6] CClientTCPSocketHandler::ClientTCPSocketHandler(wxSocketEvent&) /home/user/rpm/BUILD/aMule-2.2.6/src/ClientTCPSocket.cpp:96
[7] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) cons)
[8] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[9] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[10] wxEvtHandler::ProcessEvent(wxEvent&)
[11] wxEvtHandler::ProcessPendingEvents()
[12] wxAppConsole::ProcessPendingEvents()
[13] wxAppBase::ProcessIdle()
[14] g_main_context_dispatch()
[15] g_main_loop_run()
[16] gtk_main()
[17] wxEventLoop::Run()
[18] wxAppBase::MainLoop()
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: Stu Redman on April 04, 2011, 09:32:57 PM
Please try aMule 2.3.1 rc instead.
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: btkaos on April 05, 2011, 12:11:49 AM
macias this seems like you are using a bad wxwigdets.
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: macias on April 05, 2011, 04:54:53 PM
What do you mean by "bad"? It is downloaded from wxWidgets site.
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: btkaos on April 05, 2011, 06:10:17 PM
Quote from: macias on April 05, 2011, 04:54:53 PM
What do you mean by "bad"? It is downloaded from wxWidgets site.
Either it was incorrectly built or was incorrectly patched. As STU said, I must not be patched. (it must not be patched :))

Of course a new bug could also be a possibility, but it doesn't seem so, as you are getting the same results I had when incorrectly patching wx.
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: Stu Redman on April 05, 2011, 07:45:18 PM
Quote from: btkaos on April 05, 2011, 06:10:17 PM
As STU said, I must not be patched.
Yep, I totally said btkaos must not be patched.  ;D
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: macias on April 09, 2011, 08:14:36 AM
> Either it was incorrectly built

configure, and then make. That's all.

> or was incorrectly patched.

Not possible, I don't apply ANY patch.


Now, just for the record, this error shows when there is no connection. In my case, for a longer period of time, like 2 hours. I am not saying it is the only case, but for a few days, I lost signal (wifi) for few hours, and every time after that I got this error.
Title: Re: EncryptedStreamSocket.cpp(683): assert "false" failed in Negotiate().
Post by: Kry on April 09, 2011, 08:48:30 AM
Personally I think we've reached the point where 2.2.6 is so detached from 2.3.x that we're not really paying any attention to bugs from 2.2.6 unless they're confirmed in 2.3.1rc1