Re: [icqlib-users] TCP problems.

[Bill S. <we...@ri...>]

On Thu, 1 Feb 2001, David B wrote:

> >2. Use the icq_Log callback to capture a log.  Log everything that
> >comes across the callback, try to send a TCP message to your program.
> >Send me the resulting output.
>
> I did this, and the log was working fine, logging everything.  However
> when sending a TCP message, nothing is logged, it just plain doesn't
> see it.  So I didn't bother attaching the log as it shows nothing about
> the tcp message or any errors about it.  Let me know if you still want
> it however.

Sure, send it along, I can at least look at it, maybe something will jump
out at me.

> >3. Give me a quick description of your system, running uname -a at a
> >shell prompt is fine.
>
> I probably should have mentioned this is a win32 machine and not a unix
> machine, and there no doubt lies the problem.

Aha!  Yes, this is important... we didn't do the win32 port ourselves, and
I know nothing about win32 development, so I'm afraid I won't be much help
:(

> In the headers I have, accept is defined as:
>
> SOCKET PASCAL accept(SOCKET,struct sockaddr *,int *);
>
> Hence why I changed socklen_t for int.  However I guess this wasn't a
> good thing to do.

Ah, actually you probably made the correct change.  I doubt that's the
reason accept isn't working.

> However I had the same tcp problem with icqlib1.0 and don't remember
> any socklen_t changing in there.  Or in fact changing anything.  I
> guess it's a winsock problem if it's working ok for you on a unix based
> system.

Most likely.  If you can debug the problem and provide a patch, we'd
gladly accept it.  If you have any questions about our code, I'll be more
than happy to help.

Bil