From owner-cvs-all Mon Jun 18 12:45:14 2001 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 979B337B403; Mon, 18 Jun 2001 12:45:08 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f5IJj7r86106; Mon, 18 Jun 2001 21:45:07 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/i386 db_trace.c In-Reply-To: Your message of "Mon, 18 Jun 2001 12:37:08 PDT." Date: Mon, 18 Jun 2001 21:45:07 +0200 Message-ID: <86104.992893507@critter> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , John Baldwin writes: > >On 18-Jun-01 Poul-Henning Kamp wrote: >> Can we also please try to find some code to print a symbolic (preferably) >> or numeric traceback on panic, even if DDB is not in the kernel ? > >Well, you would just need to always compile db_trace.o into the kernel, and >then you would need to call it in the !DDB case in panic(). However, that is >quite ddb specific, so people using other kernel debuggers might object. For people who know what a kernel debugger is we can add option NOPANICTRACEBACK it would improve the quality of "my machine paniced" PRs a lot... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message