Different problem (Re: [distcc] Problems with distcc hanging on large compiles (Patch not effective))
mbp at samba.org
Thu Aug 29 20:10:01 GMT 2002
I hit Send too soon.
On 30 Aug 2002, Martin Pool <mbp at samba.org> wrote:
> In the original bug report, there was data in the sender's transmit
> queue and nothing in the receiver's receive queue. That's pretty
> strange -- it almost looks as if there is a kernel bug that is
> stopping it from being pushed across. It would help if you could
> include the output of "netstat -to" to show what the kernel thinks its
> doing, and also perhaps a tcpdump on that socket for one minute or so
> after you notice it's got into the stuck state. For example, if the
> client is on port 54522, do "tcpdump tcp port 54522". I noticed that
> in the
.. second bug report this was not the case. There was plenty of data
on the receiving side, it just wasn't reading it.
> Perhaps the strange stack shown by gdb indicates that
.. that the client has crashed and corrupted its stack.
More information about the distcc