Date: Wed, 8 Dec 2004 16:56:03 +0100 From: Michael Nottebrock <michaelnottebrock@gmx.net> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: crashdumps not working Message-ID: <200412081656.07944.michaelnottebrock@gmx.net> In-Reply-To: <200412081547.14882.michaelnottebrock@gmx.net> References: <Pine.NEB.3.96L.1041208123155.98791J-100000@fledge.watson.org> <200412081547.14882.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1447125.kpoCTPCfUL Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I played around with the kernel debug options a little and found peculiar=20 things:=20 =2D With just options KDB (and no debugger backend specified), a panic will= just=20 cause some output scroll very fast on the console - perhaps kdb is trying t= o=20 enter a nonexisting debugger backend and loops? =2D With options KDB, KDB_UNATTENDED and DDB, a panic _does_ trigger DDB,=20 contrary to what the description of KDB_UNATTENDED says. It seems to me 5.3's debugging facilities are somewhat in disarray... =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1447125.kpoCTPCfUL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBtyQXXhc68WspdLARAkcsAKCbHR+iAap7v3QE1Bs8chANAfYbWACbBMWw 1LdYay6VoHZQyhhNTlUvrB4= =hCTG -----END PGP SIGNATURE----- --nextPart1447125.kpoCTPCfUL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412081656.07944.michaelnottebrock>