From owner-freebsd-hackers  Tue Mar  2 20:31:47 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5])
	by hub.freebsd.org (Postfix) with ESMTP id 6FFA414E52
	for <freebsd-hackers@freebsd.org>; Tue,  2 Mar 1999 20:30:50 -0800 (PST)
	(envelope-from durham@w2xo.pgh.pa.us)
Received: (from durham@localhost)
	by w2xo.pgh.pa.us (8.9.1/8.9.1) id XAA08604
	for freebsd-hackers@freebsd.org; Tue, 2 Mar 1999 23:31:05 -0500 (EST)
	(envelope-from durham)
Date: Tue, 2 Mar 1999 23:31:05 -0500 (EST)
From: Jim Durham <durham@w2xo.pgh.pa.us>
Message-Id: <199903030431.XAA08604@w2xo.pgh.pa.us>
To: freebsd-hackers@freebsd.org
Subject: natd core dumps in packetBuf
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On a 3.0-RELEASE system, I've had problems with
natd core dumping. I compiled it with -g and
was able to run gdb with symbols in the last
dump.

Here's what I see...

GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc.
Core was generated by `natd'.
Program terminated with signal 11, Segmentation fault.
#0  0x280aca00 in ?? ()
(gdb) file natd
Reading symbols from natd...done.
(gdb) where
#0  0x280aca00 in ?? ()
#1  0x804c6c9 in packetBuf ()
#2  0x280570fd in ?? ()
#3  0x2805722d in ?? ()
#4  0x28056298 in ?? ()
#5  0x280569ee in ?? ()
#6  0x804977a in DoAliasing (fd=3) at natd.c:492
#7  0x8049503 in main (argc=3, argv=0xefbfd7c4) at natd.c:348
#8  0x8048ea5 in _start ()

Any ideas?

regards,
Jim Durham


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message