A quick fix to enable things to work again. The bug occurred because the socket number supplied to the socket creation/activation routine was never correctly initialised. I had thought a call to 'socket' routine returned the socket number in the first parameter, but it turns out I was supposed to _supply_ the socket number. (I had misunderstood what was hidden behind the 'SOCKET' type definition.) Oddly enough it took nearly two months before this mistake caused something to stop working (seemingly)--it seems nonsensical values didn't always cause failure. TODO: Investigate this further? TODO: FIx properly to allow multiple sockets and tracking thereof.
git-svn-id: svn+ssh://oldsvn/home/mlalondesvn/svn/cral@105 3ee9b42a-b53c-0410-a25e-f0b6218d5d5bmaster
parent
8247d829a2
commit
5e153c539e
Loading…
Reference in new issue