Creating Socket in secondary thread confusion Topic is solved

[evstevemd]

I'm creating wxSocketClient instance and I use block mode as advised

Code: Select all

    m_socket = new wxSocketClient(wxSOCKET_BLOCK|wxSOCKET_WAITALL);
    m_socket->Notify(false); //disables socket events

    wxIPV4address addr;
    addr.AnyAddress();
    addr.Service(port);

    if(m_socket->Connect(addr, true))
    {
        wxPuts(wxString::Format("Connected to port %d", port));
    }

But I get error:

../src/common/socket.cpp(1984): assert "(flags & wxSOCKET_BLOCK) || wxIsMainThread()" failed in wxSocketClient(): Non-blocking sockets may only be created in the main thread [in thread 70000611d000]

Since thread is already in blocked mode I wonder what is going on. Can someone help me understand why is it complaining that?

Here is a relevant callstack

Call stack:
[01] wxSocketClient::wxSocketClient(int) socket.cpp:1982
[02] wxSocketClient::wxSocketClient(int) socket.cpp:1988

[Kvaz1r]

Code looks ok for me. Can you provide MCVE for reproducing the behaviour?

Edit:

The documentation said one must call Initialize/0 when use wxSocket from multiple threads:

When using wxSocket from multiple threads, even implicitly (e.g. by using wxFTP or wxHTTP in another thread) you must initialize the sockets from the main thread by calling Initialize() before creating the other ones.

Can it be problem?

[evstevemd]

Hi,

Code looks ok for me. Can you provide MCVE for reproducing the behaviour?

I have been puzzled for quiet long time only to find I was modifying a copy of source files not the one in project so I was actually changing nothing on actual code I was compiling. Stupid error indeed!

The documentation said one must call Initialize/0 when use wxSocket from multiple threads:

When using wxSocket from multiple threads, even implicitly (e.g. by using wxFTP or wxHTTP in another thread) you must initialize the sockets from the main thread by calling Initialize() before creating the other ones.

Can it be problem?

It is initialized already in app's OnInit

Thanks for the comment. I have fixed it