Lacewing Socket Error

Hey,
Trying to make a custom Lacewing server. I've linked the function successfully, including On Errors, and started hosting, without problems. However, regular Lacewing MMF clients (on the server's computer, the server's network, and the internet) that are attempting to connect receive "Error connecting - Socket error" which isn't very descriptive. The firewall has been set to allow connections, but the linked On Connect function is never executed, and neither is On Error.
I'm using liblacewing as a DLL, built in Debug mode, and I'd like to know if there's a way to receive a more informative error.
Using a regular Lacewing Relay Server object works fine.
Thanks,

Did you use Lacewing::Server or Lacewing::RelayServer?

Lacewing::RelayServer.

Which version of liblacewing? Can you post your source?

I'm using 0.2.6, and the skeleton code of the server is this:

Code:

---

bool OnConnect(Lacewing::RelayServer &Server, Lacewing::RelayServer::Client &Client)
{
        Debug("OnConnect triggered (Server)."); // Does not run
        return true;
}

class Server
{
        public:
        Lacewing::RelayServer LacewingServer;
        // ...
        Server()
        {
                LacewingServer = new Lacewing::RelayServer(pExt->AppEventPump);
                LacewingServer->Tag = this;
                LacewingServer->onChannelMessage(::OnChannelMessage);
                LacewingServer->onConnect(::OnConnect);
                LacewingServer->onDisconnect(::OnDisconnect);
                LacewingServer->onError(::OnError);
                LacewingServer->onJoinChannel(::OnJoinChannel);
                LacewingServer->onLeaveChannel(::OnLeaveChannel);
                LacewingServer->onPeerMessage(::OnPeerMessage);
                LacewingServer->onServerMessage(::OnServerMessage);
                LacewingServer->onSetName(::OnSetName);

                LacewingServer->SetWelcomeMessage("Generic welcome message");
                LacewingServer->Host(6121);
                Debug("Server::Server() executed; host returns %i for Hosting.", LacewingServer->Hosting()); // Runs and shows Hosting() returns true
       
        }
}

void Extension::BootCustomServer()
{
        Debug("Creating new Server class.");
        Server * MyServer = new Server;
        Debug("Class created; server booted on port 6121.");
}

---

The actual code is much more complex, but that's how I'm using it.

I don't really see how that code would compile? "LacewingServer" isn't a pointer, but then you're using it as one.

Anyway - perhaps you could isolate this into a minimal example file, and then I can see what's going wrong (ledev.org is running a liblacewing 0.2.6 relay server at the moment and it's working fine).

That was an spelling mistake yeah, there should be a * in there.
I'll see if I can cut down the code from the original, but it's quite bulky.

Start with a new, minimal server and work up from that until it breaks.

Well, I cut down my current one by creating a new VS project and copying some of the code, and I'm encountering DLL errors again, where it compiles fine but doesn't appear in the Create Object list. I'll try to work around that and have an object here by Saturday.

On a similar note, I couldn't connect to any of the public servers yesterday. Ledev's were both reported offline by LB's PHP script, and Klikfarm was reported online, but never triggered the On Connect condition (nor did it report a timeout).

Well, I failed to work around it, but in a plain EXE program I also receive this bug. The EXE is a RelayServer (liblacewing debug build (built as part of the VS project)). It's the same code I opened 2 issues for on GitHub.
The server hosts fine, without issue, but connections just don't happen. The clients report that there's a socket error, and the servers never receive a connection, whether I use a domain, remote IP address, local IP, or localhost to connect.
Testing the program on another computer works fine, so it's this one's settings; what should I do to figure out what is whacko with this computer? Is there any tools you recommend?

Quote:

---

Originally Posted by SortaCore

Well, I failed to work around it, but in a plain EXE program I also receive this bug. The EXE is a RelayServer (liblacewing debug build (built as part of the VS project)). It's the same code I opened 2 issues for on GitHub.
The server hosts fine, without issue, but connections just don't happen. The clients report that there's a socket error, and the servers never receive a connection, whether I use a domain, remote IP address, local IP, or localhost to connect.
Testing the program on another computer works fine, so it's this one's settings; what should I do to figure out what is whacko with this computer? Is there any tools you recommend?

---

If you're using linux system you might have corrupted version of WINE exactly like I had. Upgrading to the unstable WINE version fixed my problem.

Nope, a recently fresh install of Windows XP Home Edition SP3.

I'm having an odd issue with this code:

Code:

---

#include <iostream>
#include "Lacewing.h"

int main()
{
        Lacewing::EventPump EventPump;
        Lacewing::RelayServer RelayServer (EventPump);

        RelayServer.Host();

        std::cout << Lacewing::Version() << std::endl;
        EventPump.StartEventLoop();
}

---

It prints out "liblacewing 0.3.0 (Windows/x86)" and merrily hosts along, until anything tries connecting to it. The attached MFA can be used to cause it to crash, simply by connecting.

What's the stack trace for the crash? (sorry, I'm not on Windows). You might want to stick with 0.2.6 if you're experiencing problems with 0.3.x - there were some pretty major changes for IPv6 support.

Having said that, when did you last pull from git? I think I fixed a windows server crash the other day.

I just tried using the latest version from GitHub, but in both of the DLL builds I get unresolved externals. I'll try and do some investigation though

The RelayServer::Host() function is run, it's just the program doesn't trigger any breakpoints when hit. My debug function works fine though.