Date: Sat, 28 Apr 2007 10:41:28 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-stable@freebsd.org Cc: Oleg Derevenetz <oleg@vsi.ru>, Kris Kennaway <kris@obsecurity.org>, LI Xin <delphij@delphij.net>, "Marc G. Fournier" <freebsd@hub.org> Subject: Re: How to report bugs (Re: 6.2-STABLE deadlock?) Message-ID: <200704281041.36636.doconnor@gsoft.com.au> In-Reply-To: <A5A7F962E5B9C36872977B4D@ganymede.hub.org> References: <20070313140848.GA89182@steerpike.hanley.stade.co.uk> <20070425035316.GB44054@xor.obsecurity.org> <A5A7F962E5B9C36872977B4D@ganymede.hub.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Saturday 28 April 2007 04:33, Marc G. Fournier wrote: > A thought: how hard would it be to add some method of forcing a > system crash, that would dump core, from the command line? Something > that, by default, would be disabled, but for remote debugging > purposes, one could enable in the kernel and do a 'sysctl > kernel.force_core_crash=1' to have it do it? I imagine that having a > core to analyze would allow providing more information then nothing > at all, no? I think you can do this.. sysctl debug.kdb.panic=1 Alas that appears to be a -current thing. 6.x has debug.kdb.enter though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBGMp9I5ZPcIHs/zowRAj48AJ4snjz//IPO5190ajBg/qhCdeLgIwCgjE39 qMPEdFIFY/r1PZvqTEZAjHk= =tGB0 -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704281041.36636.doconnor>