From owner-freebsd-questions Fri Sep 10 1:43:43 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 6CADA151EA for ; Fri, 10 Sep 1999 01:43:40 -0700 (PDT) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.8.8/8.8.8) with ESMTP id TAA08844; Thu, 9 Sep 1999 19:00:27 -0700 (PDT) (envelope-from bright@wintelcom.net) Date: Fri, 10 Sep 1999 02:00:27 +0000 (GMT) From: Alfred Perlstein To: Decebal Topala Cc: questions@FreeBSD.ORG Subject: Re: Re: don't fork bomb In-Reply-To: <199909100830.LAA11465@atlas.dnt.md> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Sep 1999, Decebal Topala wrote: > > > Is it possible for you to get a crash dump and give a traceback? > > > How to do this ??? there should be a section on this in the handbook, but here's the short and sweet way: compile a new kernel, give the option "-g" to config: "config -g mykernel" after installing add this line to /etc/rc.conf: dumpdev="/dev/myswap_partition" make sure /var/crash is a directory (or a symlink to a directory) with enough free space (amount of ram) reboot... ok of you crash the box then there should be a few files in /var/crash, try this: cd /var/crash gdb -k /kernel vmcore.0 (if the machine just locks up try ctrl+alt+esc, then type "panic" and hit enter) if you have problems consult the handbook and FAQ. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message