sending byte <= -112

**abraham2119** · 07-24-2009

Hello,

I have a simple networking application. Everything runs perfectly well. The server is programmed in C, while the client is programmed in Java.

The only thing is that when the server tries to send a byte <= then -112, the client receives it as 63. Any byte greater than -112 sends successfully.

Is there a specific reason as to why this is occurring?

Thank you,
abraham2119

EDIT: I was during some tesing and it turns out to be that it only sends the bytes: -112, -113, -115 incorrectly. The client receives them as 63.

**bithub** · 07-24-2009

Is there a specific reason as to why this is occurring?

Either a bug in the send code, or a bug in the receive code. Without seeing the code though, we can't give much help.

**abraham2119** · 07-24-2009

I doubt it is a bug of either the receiving or sending code since when the client writes either one of the bytes (-112, -113, -115) the server receives it as 63, and the same happens vice versa (server sends one of those bytes to the client, and client receives it as 63).

Anyways, here is my server's send code:

Code:

int writef(sock *s, char *buff, int tosend)
{
    int sent = 0;
    while (sent != tosend) {
        int _sent = send((SOCKET) *s, buff+sent, tosend-sent, 0);
        if (_sent >= 0)
            sent += _sent;
        else
            return SOCKET_ERROR;
    }

    return 0;
}

I invoke the method as follows:

Code:

char buff[2];
buff[0] = -112;
buff[1] = 5;

writef(&conn, buff, 2);

Here is my server's receive code:

Code:

char buff[512];
recv(conn, buff, 512, 0);

I am also inclined into thinking that this bug has to do with the server since when setting up a server written in Java, it all works well. I also do not believe it has anything to do with the byte's signedness since it receives other negative numbers perfectly fine.

Thanks again,
abraham2119

**bithub** · 07-24-2009

I don't see how the code you posted can send a byte with a value of 63.

and client receives it as 63

Can you post the Java code that receives 63 when that code you posted above is executed?

**abraham2119** · 07-24-2009

I wrote a sample application that illustrates my problem.

Run the server and then the client, and the client will print out a question mark character, which has the value of 63.

Here is the sample server and client: abraham2119 private pastebin - collaborative debugging tool

**tabstop** · 07-24-2009

Originally Posted by abraham2119

I wrote a sample application that illustrates my problem.

Run the server and then the client, and the client will print out a question mark character, which has the value of 63.

Here is the sample server and client: abraham2119 private pastebin - collaborative debugging tool

Well now, that's an interesting statement right there. Is ? being printed because you are receiving a byte of 63, or because you are asking the terminal to print an unprintable character? Can you check whether value==63 after receiving?

**slingerland3g** · 07-24-2009

How do you expect the while loop you have send() defined within to terminate? From what I can tell your sent variable will just keep growing. Unless you are forcing a socket error on your client side to close the connection.

**bithub** · 07-24-2009

Yeah, change your print statement to:

Code:

System.out.println((int)line.charAt(0));

I'm willing to bet you get 144 which is the 2s compliment of -112.

**bithub** · 07-24-2009

Originally Posted by slingerland3g

How do you expect the while loop you have send() defined within to terminate? From what I can tell your sent variable will just keep growing. Unless you are forcing a socket error on your client side to close the connection.

The while loop terminates when sent == tosend.

**slingerland3g** · 07-24-2009

Originally Posted by bithub

The while loop terminates when sent == tosend.

True, but that is under the assumption...

Code:

  sent += _sent   /* Must equal to 2 to stop */

Are we sure this will happen?

**bithub** · 07-24-2009

Are we sure this will happen?

If there is no socket error, then this will happen.

**iMalc** · 07-24-2009

Originally Posted by slingerland3g

How do you expect the while loop you have send() defined within to terminate? From what I can tell your sent variable will just keep growing. Unless you are forcing a socket error on your client side to close the connection.

Look closer. The condition in the while loop will become true and the fucntion will return zero. It should work just fine.

**slingerland3g** · 07-24-2009

Originally Posted by bithub

If there is no socket error, then this will happen.

As far as the logic goes with verifying the amount of bytes sent for _sent, the else statement for SOCKET_ERROR will never get reached because of that. My assumption is that this socket is continuing to write data. I would simply check that sent is eventually to equal 2. I would add a printf in there to double check, unless I am not seeing(understanding) something here. I guess that buff is one byte here being sent. And the second time around another byte. Then this may be feasible and thus will terminate as expected.

**iMalc** · 07-24-2009

If one was less trusting of the API, then it might be considered safer for the while loop condition to have been:

Code:

while (sent <= tosend)

But it should work as-is.

**bithub** · 07-24-2009

the else statement for SOCKET_ERROR will never get reached because of that.

Yes it will. If send returns -1 (which it does on error), then the SOCKET_ERROR statement will be reached.

My assumption is that this socket is continuing to write data.

It continues to write data until the correct amount of bytes has been sent or send() has returned an error.

I would simply check that sent is eventually to equal 2

If by "2" you mean tosend, then that's what he is doing.

Thread: sending byte <= -112

Thread Tools

Search Thread

Display

sending byte <= -112

Similar Threads

Sending a byte down serial pipe

brace-enclosed error

About aes

Need some help regarding data structures

error: identifier "byte" is undefined.