1.1.6 crashes on OpenBSD 2.8

Rafal Maszkowski rzm@icm.edu.pl
Tue Jul 16 20:27:47 UTC 2002

dccm from DCC 1.1.6 crashes (and sometimes even worse - stalls) on OpenBSD 2.8:

root@gw:/var/dcc,0# gdb libexec/dccm dccm.core
GNU gdb 4.16.1
Copyright 1996 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-openbsd2.8"...
Core was generated by `dccm'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/libexec/ld.so...done.
Reading symbols from /usr/lib/libm.so.0.1...done.
Reading symbols from /usr/lib/libc_r.so.3.1...done.
#0  0x400a5c2f in _thread_machdep_switch ()

(gdb) bt
#0  0x400a5c2f in _thread_machdep_switch ()
#1  0x400f2308 in _sigq_check_reqd ()
#2  0x400a4e36 in _thread_kern_sched_state ()
#3  0x400bbd06 in select ()
#4  0xe5c0 in dcc_clnt_op (emsg=0x54328 "", ctxt=0x2bac10, anum=-1, msg=0x2ccc14, msg_len=188, op=DCC_OP_REPORT, resp=0x2ccb6c,
    resp_max_len=168, resp_su=0x0) at clnt_send.c:1877
#5  0x9e7d in dcc_ask (emsg=0x54328 "", ctxt=0x2bac10, header=0x547ec, cks=0x5490c, honorp=0x54e28 "", local_tgts=1) at ask.c:70
#6  0x492b in ask_dcc (wp=0x5406c) at dccm.c:1742
#7  0x548b in dccm_eom (ctx=0x4c600) at dccm.c:2046
#8  0x89f3 in st_bodyend ()
#9  0x7e9e in mi_engine ()
#10 0x7065 in mi_handle_session ()
#11 0x6965 in mi_thread_handle_wrapper ()
#12 0x40061584 in _thread_start ()
#13 0x17 in ?? ()
Cannot access memory at address 0xffffffff.

root@gw:/var/dcc,0# uname -a
OpenBSD gw 2.8 MKUR#0 i386

root@gw:/var/dcc,0# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-unknown-openbsd2.8/2.95.3/specs
gcc version 2.95.3 19991030 (prerelease)

Avec mes souvenirs/J'ai allumé le feu
Mes chagrins, mes plaisirs/Je n'ai plus besoin d'eux!

More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.