Date: Mon, 3 Dec 2001 16:40:09 -0800 (PST) From: Archie Cobbs <archie@packetdesign.com> To: FreeBSD-gnats-submit@freebsd.org Subject: docs/32483: developers handbook should mention debug.enter_debugger Message-ID: <200112040040.fB40e9R31087@bubba.packetdesign.com>
next in thread | raw e-mail | index | archive | help
>Number: 32483 >Category: docs >Synopsis: developers handbook should mention debug.enter_debugger >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Dec 03 16:50:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Archie Cobbs >Release: FreeBSD 4.4-STABLE i386 >Organization: Packet Design >Environment: System: FreeBSD bubba.packetdesign.com 4.4-STABLE FreeBSD 4.4-STABLE #1: Mon Oct 22 15:26:21 PDT 2001 root@:/usr/obj/usr/src/sys/BUBBA i386 >Description: The FreeBSD developer's handbook, in the chapter on kernel debugging, in the sections "On-line Kernel Debugging..." it doesn't seem to mention that there is a very easy way to make the kernel drop into DDB or GDB from the command line. You simply say one of these commands: $ sysctl -w debug.enter_debugger=ddb or $ sysctl -w debug.enter_debugger=gdb and the kernel immediately drops into the debugger. Often it's more convenient to let a system boot fully and then do the above gdb command that trying to rig up gdb from the boot prompt. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112040040.fB40e9R31087>