Fix UDP socket bug (XCC)
authorBarret Rhoden <brho@cs.berkeley.edu>
Fri, 23 Oct 2015 18:26:07 +0000 (14:26 -0400)
committerBarret Rhoden <brho@cs.berkeley.edu>
Wed, 28 Oct 2015 16:05:14 +0000 (12:05 -0400)
commit3e0732ed32e05f4c7148c3a6b3481bf67ab4e897
tree13aa28a6e6f9f82e0a98cfa3eff6bfaedb7935f8
parenta0c87710776335921e6a71335e2c95ab81599c61
Fix UDP socket bug (XCC)

All UDP sockets were pointing at conversation 0.  We would successfully
clone a new UDP conversation, but when we attempted to read the ctl
file, we'd get an empty string back instead of the conversation ID.
That worked if our conversation happened to be 0, but otherwise would
fail.

The root cause was that we advanced the offset by 7 when we wrote the
"headers" command for UDP sockets.  We need to reset the chan back to 0
before reading.

Rebuild glibc.

Signed-off-by: Barret Rhoden <brho@cs.berkeley.edu>
tools/compilers/gcc-glibc/glibc-2.19-akaros/sysdeps/akaros/socket.c