Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[macias]

• openSUSE 11.4,
• 64-bit,
• wxGTK 2.8.12 compiled myself + patch provided by Kry:
  http://forum.amule.org/index.php?topic=18506.msg101034#msg101034
• aMule 2.2.6 compiled myself

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()


[Stu Redman]

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.

[macias]

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()



[Stu Redman]

Please try aMule 2.3.1 rc instead.

[btkaos]

macias this seems like you are using a bad wxwigdets.

[macias]

What do you mean by "bad"? It is downloaded from wxWidgets site.

[btkaos]

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.

[Stu Redman]

As STU said, I must not be patched.

Yep, I totally said btkaos must not be patched. 

[macias]

> 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.

[Kry]

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