Date: Tue, 13 Jul 2004 12:28:20 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Lukas Ertl <le@freebsd.org> Cc: current@freebsd.org Subject: Re: sysctl debug.debugger_on_panic Message-ID: <20040713192820.GA8979@dhcp50.pn.xcllnt.net> In-Reply-To: <20040713211037.M547@korben.in.tern> References: <20040713203158.E548@korben.in.tern> <20040713190119.GB8872@dhcp50.pn.xcllnt.net> <20040713190653.GC8872@dhcp50.pn.xcllnt.net> <20040713211037.M547@korben.in.tern>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 13, 2004 at 09:16:53PM +0200, Lukas Ertl wrote: > On Tue, 13 Jul 2004, Marcel Moolenaar wrote: > > >I took the time to go over the detailed information you sent about > >your system (yes, I'm sarcastic -- no such information has been > >sent) and I can only assume it's your fault :-) > > The system is an IA32 based server, running an up-to-date -CURRENT. I > have KDB and DDB in the kernel. Up to the DDB change, I set the sysctl to > 0 and have the box automatically dump core and reboot, if I trigger a > KASSERT or run into a plain NULL pointer dereference. Now, it just sits a > the DDB prompt. If you need more info, let me know what's needed. A backtrace would be nice. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040713192820.GA8979>