Subject: port-hpcmips/21326: dsniff dumps core on hpcmips
To: None <gnats-bugs@gnats.netbsd.org>
From: None <netbsd@davidkrause.com>
List: netbsd-bugs
Date: 04/26/2003 05:47:42
>Number:         21326
>Category:       port-hpcmips
>Synopsis:       dsniff dumps core on hpcmips
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-hpcmips-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 26 05:48:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     David Krause
>Release:        NetBSD 1.6.1
>Organization:
>Environment:
NetBSD bean.davidkrause.com 1.6.1 NetBSD 1.6.1 (GENERIC) #0: Tue Apr  8 08:06:53 UTC 2003     autobuild@tgm.daemon.org:/autobuild/netbsd-1-6/hpcmips/OBJ/autobuild/netbsd-1-6/src/sys/arch/hpcmips/compile/GENERIC hpcmips

>Description:
dsniff dumps core on hpcmips

bean# pkg_info | grep dsniff
dsniff-2.3          password sniffer

reproducible on 1.6.1 and -current

>How-To-Repeat:
bean# dsniff -n
dsniff: listening on wi0
Segmentation fault (core dumped)

also happens on ne0

bean# gdb -q /usr/pkg/sbin/dsniff dsniff.core
(no debugging symbols found)...Core was generated by `dsniff'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/libexec/ld.elf_so...done.
Loaded symbols for /usr/libexec/ld.elf_so
Reading symbols from /usr/lib/libresolv.so.1...done.
Loaded symbols for /usr/lib/libresolv.so.1
Reading symbols from /usr/lib/libpcap.so.1...done.
Loaded symbols for /usr/lib/libpcap.so.1
Reading symbols from /usr/pkg/lib/libnet.so.1...done.
Loaded symbols for /usr/pkg/lib/libnet.so.1
Reading symbols from /usr/lib/libssl.so.2...done.
Loaded symbols for /usr/lib/libssl.so.2
Reading symbols from /usr/lib/libcrypto.so.1...done.
Loaded symbols for /usr/lib/libcrypto.so.1
Reading symbols from /usr/lib/libc.so.12...done.
Loaded symbols for /usr/lib/libc.so.12
#0  0x416234 in mkhash ()
(gdb) bt
#0  0x416234 in mkhash ()
#1  0x413d14 in detect_scan ()
warning: Warning: GDB can't find the start of the function at 0x19d20016.

    GDB is unable to find the start of the function at 0x19d20016
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x19d20016 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.

>Fix:
unknown
>Release-Note:
>Audit-Trail:
>Unformatted: