From owner-freebsd-hackers Tue Nov 9 7: 5:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id B771B14D7F for ; Tue, 9 Nov 1999 07:05:17 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id KAA28385 for ; Tue, 9 Nov 1999 10:05:15 -0500 (EST) Date: Tue, 9 Nov 1999 08:52:58 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: How to use gdb to catch a panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have set up an environment of remote serial debugging on FreeBSD 3.3-Release. I have a program that whenever it runs the kernel panics. Is there any way I can use remote serial debugging to trace this panic process instead of examining a dead kernel (i.e., coredump)? Or, is there any way I can use to drop the debugged kernel to debugger mode whenever it runs a certain piece of code? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message