minor bug in nsd-xfer

Stephane Bortzmeyer bortzmeyer at nic.fr
Fri Feb 4 09:49:10 UTC 2005

On Fri, Feb 04, 2005 at 10:34:06AM +0100,
 Peter Larsen <mail at czar.dk> wrote 
 a message of 47 lines which said:

> (gdb) bt
> #0  0x281d1557 in read () from /lib/libc.so.5
> #1  0x0804b63e in read_socket (s=3, buf=0xbfbf28b2, size=2) at nsd-xfer.c:300
> #2  0x0804b735 in receive_response (state=0xbfbf4884) at nsd-xfer.c:493
> #3  0x0804c259 in main (argc=252, argv=0xbfbfea60) at nsd-xfer.c:695

This is what I expected and, indeed, I believe my patch fixes
this. (You can use truss, too, since it displays the return code of
read, it will be one more proof.)

More information about the nsd-users mailing list