[Gambas-user] Really weird socket problem

[Kad Mann]

I need pointers on where I might look to solve this.

I've written a proxy class in gambas (2.16) and it was working
brilliantly when I went to be last night and left it running. When I got
up this morning my Linux desktop, which was running the compiled gambas
program, note compiled program - not inside the IDE, displayed a message
about a broken pipe in the proxy class. I didn't get the message in full
(my bad), but it was very brief and didn't say much more than "cProxy:
broken pipe error".

On investigating, my Windows server had rebooted (hahaha stupid MS patch
got auto-installed) and ever since, my gambas proxy does not work
anymore on the local machine.

I went back through eight known good revisions of the code (I save
working revisions as I go, just in case something like this happens due
to an error on my part) but not a single one of them works at all.
Therefore I know it's not my code that is the problem.

I put some debugs into the latest code and this is what I get:

1. cProxy.StartProxyServer.42: StartProxyServer
2. cProxy.ProxyServer_Connection.53: ProxyServer_Connection
3. cProxy.Socket_Ready.124: Socket_Ready
4. cProxy.KillProxy.176: KillProxy

At 1, the proxy is started and is listening.

At 2, a connection is received at the proxy from a client application,
in this case Pan or SeaMonkey.

At 3, the socket is established and ready to talk.

Between 3 and 4, several different clients (Pan and Seamonkey) exhibit
the same symptoms, they behave as if there is no communication on the
socket. Pan resets the connection and keeps trying. Seamonkey just waits
and waits.

At 4, the proxy has detected that the client connection has gone away so
it kills the remote connection and starts listening for more incoming
client connections, which is what the KillProxy procedure is suppsoed to
do.

I tried pointing the clients to localhost and 127.0.0.1, with different
port values, all above 5000. In desperation I tried 119 on the
localhost. Still no change. I rebooted twice. My Ubuntu has not been
updated since last week.

Finally I tried the socket example that comes with gambas. It too fails
to connect with itself. It says "Host found. Connecting...", then some
10 or 15 seconds later, it says "Timeout trying to stablish [sic]
connection".

My gambas appears to be b0rked. Perhaps the solution is to uninstall
gambas and recompile it, but I'd prefer to find out why it blew up the
way it did.

Anyone care to try and shed some light on this weird issue? Could a
crashed pipe cause a compiled gambas application to scribble all over
itself and damage the socket component in the same deal?