Date: Sun, 22 Feb 2004 19:12:19 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Bruce Evans <bde@zeta.org.au> Cc: cvs-all@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: <7mptc7jud8.wl@black.imgsrc.co.jp> In-Reply-To: <7m3c99vp6i.wl@black.imgsrc.co.jp> References: <200401192127.i0JLRBL3041817@repoman.freebsd.org> <20040120175334.W3279@gamplex.bde.org> <20040213035557.M24031@gamplex.bde.org> <7mfzdexjzs.wl@black.imgsrc.co.jp> <20040215094444.F6303@gamplex.bde.org> <7m3c99vp6i.wl@black.imgsrc.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
At Tue, 17 Feb 2004 21:57:41 +0900,
kuriyama wrote:
> But I personally feel this should be back out after re-reading and we
> should tackle traceback() improvements.
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.
=46rom my (non kernel hacker) understanding, I'm not sure whether this
is possible and preferred approach or not. How about this approach?
o Add DDB_BACKTRACE_ONLY option.
o Compile minimal code for db_print_backtrace() into the kernel (some
#ifdef storm?) when this option is enabled without DDB.
o Call backtrace() if this option is enabled like as DDB_TRACE.
o Enable this option in GENERIC by default.
--=20
Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
<kuriyama@FreeBSD.org> // FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mptc7jud8.wl>