I've updated distcc from 2.16 to 2.17 and I'm experiencing crashes.
The crash seems to be related to changes in the client part of distcc because:
- I can reproduce the crashes with
* server distccd 2.16 + client distcc 2.17
* server distccd 2.17 + client distcc 2.17
- I can't reproduce the crashes with
* server distccd 2.16 + client distcc 2.16
* server distccd 2.17 + client distcc 2.16
Our compilation farm runs Red Hat Linux 9 machines. Many of these machines are currently offline, which means the new timeout code may be triggered often. ...
How to debug this? I'm not even sure whether it's distcc or g++ segfaulting. Since I don't run out of memory and a build with distcc 2.16 succeeds, I guess that's distcc failing.
I do get core files in the build directory, but I'm not sure what to do with them since the debugger thinks they're not from distcc:
$ gdb /usr/local/distcc/bin/distcc aimsalgo-linux-default/src/aimsalgo/core.20711
[...]
warning: core file may not match specified executable file.
Core was generated by `g++ -c -Wall -W -D_REENTRANT -DCARTO_DEBUGMODE="default" -DAIMS -I/home/usernam'.
Program terminated with signal 11, Segmentation fault.
gdb is telling you it's from g++. So g++ is crashing, not distcc. Try updating the g++ RPM on your build servers? - Dan
__ distcc mailing list http://distcc.samba.org/
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc
