Date: Mon, 21 Aug 1995 09:12:38 -0700 (PDT) From: Julian Elischer <julian@ref.tfs.com> To: henrich@crh.cl.msu.edu (Charles Henrich) Cc: freebsd-hackers@freebsd.org Subject: Re: How do I save panic messages?! Message-ID: <199508211612.JAA23746@ref.tfs.com> In-Reply-To: <199508201502.LAA01118@crh.cl.msu.edu> from "Charles Henrich" at Aug 20, 95 11:02:04 am
next in thread | previous in thread | raw e-mail | index | archive | help
The best way is to switch back to an non-X console (CTL-ALT-F1) before testing your change! then you should be able to see what comes up when you do your test.. if it doesn't crash, use ALT-F4 to switch back to X and keep working.. in adition, you can save a corefile of the crash if you've config'd the kernel correctly and dump out the command buffer in it when you've rebooted.. not to mention running gdb on the saved corefile to get a stack-trace and other nice goodies.. (see man savecore, man gdb etc.) julian > > This is getting tedious, Im attempting to work on significant port of kernel > level code, but if Im not sitting on virtual console 0, whenever the system > panics, Im screwed. I cant switch out of X, or kill the screen blanker, or > switch to the virtual console to see what the hell went wrong, nor is any > information logged anywhere :(. Any help is most gratefully appreciated. > > -Crh > > Charles Henrich Michigan State University henrich@crh.cl.msu.edu > > http://rs560.msu.edu/~henrich/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508211612.JAA23746>