Date: Mon, 1 Jan 2007 15:57:46 +0100 From: Stefan Bethke <stb@lassitu.de> To: Chris <chrcoluk@gmail.com> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: 6.2-PRE: Fatal Trap? Message-ID: <C416E76B-A709-4BA8-8C52-69734DCE511E@lassitu.de> In-Reply-To: <3aaaa3a0701010331u72d70e90p714a0171fe9f292a@mail.gmail.com> References: <20061230035722.L39715@thebighonker.lerctr.org> <4596543D.2090700@orchid.homeunix.org> <en5ldl$1tp$1@sea.gmane.org> <3aaaa3a0701010331u72d70e90p714a0171fe9f292a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 01.01.2007 um 12:31 schrieb Chris: > Is it possible to make it auto run debugger, then auto run backtrace > then dump the output to disk so people who have no local access can > get backtraces? No, but you can enable crashdumps and run the debugger on the dump afterwards. Add dumpdev="AUTO" to /etc/rc.conf, then run /etc/rc.d/dumpon start. When the next panic occurs, the kernel will write the dump to the configured swap space, and the system will save the dump to /var/crash on rebooting. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ kerneldebug-gdb.html on how to get a backtrace from that dump. If you're short on space in /var, and/or you have a large amount of RAM, you can set the sysctl debug.minidump to 1 to have the kernel only dump relevant portions of memory, instead of everything. This, however, is experimental in -stable, afaik. Stefan -- Stefan Bethke <stb@lassitu.de> Fon +49 170 346 0140
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C416E76B-A709-4BA8-8C52-69734DCE511E>