Date: Thu, 29 Jun 2000 17:08:20 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> Cc: David Gilbert <dgilbert@velocet.ca>, Freebsd-stable@FreeBSD.ORG Subject: Re: dc19 fructration. Message-ID: <20000629170820.D275@fw.wintelcom.net> In-Reply-To: <200006300000.RAA00417@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Thu, Jun 29, 2000 at 05:00:16PM -0700 References: <14683.31607.612798.996185@trooper.velocet.net> <200006300000.RAA00417@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Rodney W. Grimes <freebsd@gndrsh.dnsmgr.net> [000629 17:00] wrote: > > >>>>> "Alfred" == Alfred Perlstein <bright@wintelcom.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000629170820.D275>