core dump while killing argus

[Peter Van Epp]

	I just killed an argus_bpf (2.0.0W) on FreeBSD 4.2-RELEASE:


test4# ps auxw | grep argus
root     166  0.0  2.1  2428 1288  p0  S     9:36PM   0:00.57 argus_bpf -w argus
.log
root     167  0.0  1.6  2136  976  p0  S     9:36PM   0:00.27 argus_bpf -w argus
.log
root     168  0.0  1.8  2272 1112  p0  S     9:36PM   0:00.20 argus_bpf -w argus
.log
test4# kill -HUP 166
test4# !ps
ps auxw | grep argus
[1]  + Done                          argus_bpf -w argus.log
test4# ls
.cshrc          .login_conf     .profile        argus.log
.history        .mail_aliases   .rhosts         argus_bpf.core
.login          .mailrc         .shrc

	And got a core (although it looks to have shut down correctly):

test4# gdb argus_bpf argus_bpf.core
GNU gdb 4.18
Copyright 1998 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-freebsd"...
(no debugging symbols found)...
Core was generated by `argus_bpf'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libm.so.2...(no debugging symbols found)...done.
Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done.
Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...
done.
#0  0x8050ea4 in ArgusWriteOutSocket ()
(gdb) where
#0  0x8050ea4 in ArgusWriteOutSocket ()
#1  0x804e701 in ArgusHandleData ()
#2  0x8050c65 in ArgusReadSocket ()
#3  0x804dbf1 in ArgusOutputProcess ()
#4  0x804d3a9 in ArgusInitOutput ()
#5  0x804a51e in main ()
#6  0x8049a89 in _start ()
(gdb)

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada