Mortissus

Hi everyone!

I have a strange error in my application. After many recv calls, the next call receives less bytes than sent by the client. For example, the client sends 70 bytes and the server receives 40 bytes. It is important to notice that, after the first call to recv is made, perror prints "Illegal Seek". But even with this error, the server receive all the bytes sent by the client in the first calls. We print perror before the recv and, before the first call, perror prints "Sucess" (probaly to a select call).

Thanks any insight!

Salem

'x' bytes sent in one send call does not guarantee that 'x' bytes will be in any single recv call.

Without seeing code, who knows what you've done

__________________
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.

Mortissus

I understand. I have prepared the code to send in many chunks, as necessary. The Illegal Seek is still there, but I think it was my mistake to consider this as an error, since recv does not return -1, therefore not setting errno. I thought that could be poor kernel code, a system call inside recv that was not beeing handled. I was a fool to think that. Anyway! The code is now working, and the lesson is, even if the client can receive 500B in one chunk, does not means that the server can receive this amount in one chunk too.

Thanks!