Date: Wed, 25 Apr 2018 09:54:55 -0700 From: John Baldwin <jhb@freebsd.org> To: Conrad Meyer <cem@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r332959 - head/sys/kern Message-ID: <5237617.Ai8m1U92WL@ralph.baldwin.cx> In-Reply-To: <201804241854.w3OIsKuQ083232@repo.freebsd.org> References: <201804241854.w3OIsKuQ083232@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, April 24, 2018 06:54:20 PM Conrad Meyer wrote: > Author: cem > Date: Tue Apr 24 18:54:20 2018 > New Revision: 332959 > URL: https://svnweb.freebsd.org/changeset/base/332959 > > Log: > panic: Optionally, trace secondary panics > > To diagnose and fix secondary panics, it is useful to have a stack trace. > When panic tracing is enabled, optionally trace secondary panics as well. > > The option is configured with the tunable/sysctl debug.trace_all_panics. > > (The original concern that inspired only tracing the primary panic was > likely that the secondary trace may scroll the original panic message or trace > off the screen. This is less of a concern for serial consoles with logging. > Not everything has a serial console, though, so the behavior is optional.) Note that KDB_TRACE is enabled by default, so you would need it to always default to false to preserve existing behavior by default. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5237617.Ai8m1U92WL>