From owner-freebsd-alpha Tue Feb 12 14:32:23 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0689037B405 for ; Tue, 12 Feb 2002 14:32:16 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA28174; Tue, 12 Feb 2002 17:32:16 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g1CMVk262195; Tue, 12 Feb 2002 17:31:46 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15465.38866.52117.177872@grasshopper.cs.duke.edu> Date: Tue, 12 Feb 2002 17:31:46 -0500 (EST) To: "Craig Burgess" Cc: "alpha" Subject: Re: wierdness on PC164 w/ 4.4-R In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Craig Burgess writes: > # pid 141 (natd), uid 0: exited on signal 10 (core dumped) > > At this rate, is there anything to lose if I get -stable? Is there > a better way to troubleshoot/fix it? I think somebody else was complaining about natd. Might have been you. What did you upgrade from? Natd hasn't changed much between 4.1 and 4.4, according to the CVS logs. I'd suggest upgrading to -stable, then building natd with symbols & seeing if you can get a stacktrace with gdb. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message