Date: Mon, 7 Jan 2013 19:23:07 -0500 From: Ryan Stone <rysto32@gmail.com> To: Xin LI <d@delphij.net> Cc: Konstantin Belousov <kostikbel@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: sysctl -a causes kernel trap 12 Message-ID: <CAFMmRNwq76vfTtBjEr_B7RVwHnHdY738oO%2Ba=rTCRfr-fs5X%2Bw@mail.gmail.com> In-Reply-To: <CAFMmRNwv8pDsy0ZRLXzUft7A1OGxEt9DSmYN1Hun7FxrbHYvnA@mail.gmail.com> References: <50EB602F.9050300@delphij.net> <20130108000233.GZ82219@kib.kiev.ua> <50EB63A9.50903@delphij.net> <CAFMmRNwv8pDsy0ZRLXzUft7A1OGxEt9DSmYN1Hun7FxrbHYvnA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 7, 2013 at 7:21 PM, Ryan Stone <rysto32@gmail.com> wrote: > Have you tried dropping into the debugger by setting > debug.debugger_on_panic=1 instead of trying to generate a core? You might > have some success generating at least a backtrace. > Sigh, reading comprehension fail on my part. Try generating a core, I guess. Another think that you could do would be to annotate the sysctl code path to print the name of the sysctl that it is about to run to the console.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNwq76vfTtBjEr_B7RVwHnHdY738oO%2Ba=rTCRfr-fs5X%2Bw>