I've noticed that dialog4ports has been crashing pretty consistently recently. Happening to anyone else?
Dan root@winbsd:/usr/ports/net-mgmt # cd zabbix2-agent/ root@winbsd:/usr/ports/net-mgmt/zabbix2-agent # ls Makefile dialog4ports.core root@winbsd:/usr/ports/net-mgmt/zabbix2-agent # gdb `which dialog4ports` dialog4ports.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 "amd64-marcel-freebsd"... Core was generated by `dialog4ports'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libncursesw.so.8...done. Loaded symbols for /lib/libncursesw.so.8 Reading symbols from /lib/libm.so.5...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /usr/lib/libdialog.so.7...done. Loaded symbols for /usr/lib/libdialog.so.7 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000800fedffa in kill () from /lib/libc.so.7 (gdb) where #0 0x0000000800fedffa in kill () from /lib/libc.so.7 #1 0x0000000800f8c4c0 in __stack_chk_fail () from /lib/libc.so.7 #2 0x0000000800f8c430 in __stack_chk_fail () from /lib/libc.so.7 #3 0x00000000004029aa in main (argc=<value optimized out>, argv=<value optimized out>) at dialog4ports.c:212 _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
