From owner-freebsd-stable Thu Jun 29 17: 8:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D0C0737C230 for ; Thu, 29 Jun 2000 17:08:26 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e5U08KI23797; Thu, 29 Jun 2000 17:08:20 -0700 (PDT) Date: Thu, 29 Jun 2000 17:08:20 -0700 From: Alfred Perlstein To: "Rodney W. Grimes" Cc: David Gilbert , Freebsd-stable@FreeBSD.ORG Subject: Re: dc19 fructration. Message-ID: <20000629170820.D275@fw.wintelcom.net> References: <14683.31607.612798.996185@trooper.velocet.net> <200006300000.RAA00417@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006300000.RAA00417@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Thu, Jun 29, 2000 at 05:00:16PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Rodney W. Grimes [000629 17:00] wrote: > > >>>>> "Alfred" == Alfred Perlstein writes: > > > > Alfred> Using truss or gdb on ifconfig may help you find out which > > Alfred> syscall is the culpret. > > > > Problem is that the system crashes before ifconfig -a completes, and > > it would appear that the stack smashing that whatever syscall is > > running does will bring down the kernel regardless of how I proceed. Ok guys, the idea behind using truss was just this: > > Problem is that the system crashes before ifconfig -a completes, and Therefore I wanted to see on which syscall the system blew up. Showing me the truss output from a successful run doesn't help. :( The idea was that it would like this: truss output.. truss output.. truss output.. truss output.. panic -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message