RE: euTcp4u bug
- Posted by Ray Smith <smithr at ix.net.au> Apr 13, 2002
- 372 views
Hi Chris, Thanks for the info, I'll have a look into it. I think the tcp4u recv function returns the exact number of bytes received. I should be able to change peek_sequence to a for loop to return whatever is in the buffer. I'll do some more investigation to see if it will effect anything else. Thanks again, Ray Smith http://rays-web.com Chris Bensler wrote: > Here is the fix: > > tcp4u.ew:201 > while (len=0 and tmp != 0) or i<len do > > > Chris > > Chris Bensler wrote: > > tcp4u_receive() doesn't handle null characters. > > > > The string returned is always peeked as a 0-terminated string. I can't > > receive a full data stream that contains nulls. > > > > The actual routine itself is written correctly, but the peek_sequence() > > routine is flawed. It catches nulls before len is reached. > > > > Chris