Date: Mon, 23 Feb 2004 00:30:52 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no> Cc: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha support.s src/sys/i386/i386 swtch.s src/sys/kern kern_shutdown.c src/sys/sys systm.h Message-ID: <20040222235120.E12791@gamplex.bde.org> In-Reply-To: <xzpr7wnweeu.fsf@dwp.des.no> References: <200401192127.i0JLRBL3041817@repoman.freebsd.org> <20040213035557.M24031@gamplex.bde.org> <20040215094444.F6303@gamplex.bde.org> <7m3c99vp6i.wl@black.imgsrc.co.jp> <7mptc7jud8.wl@black.imgsrc.co.jp> <xzpr7wnweeu.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Feb 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote: > Jun Kuriyama <kuriyama@imgsrc.co.jp> writes: > > I checked something around backtrace(). A db_print_backtrace() is > > depending on DDB, but as Bruce said, DDB is dangerous for default > > feature for -stable release. > > No, just make sure DDB_UNATTENDED is also the default. DDB_UNATTENDED doesn't work right yet. Its only effect is to clear the debugger_on_panic variable, which controls entries to the debugger on panics and on fatal traps. The following entries to the debugger are not controlled: - someone attending the console and hitting the Debugger hotkey. - stray Debugger() calls in source code. There is now a non-stray one in watchdog_fire(). - stray breakpoints in source code or left over from previous debugging session. - stray trace traps, perhaps from trace flags set in previous debugging session (these can be deep in stacks and hard to kill). Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040222235120.E12791>