Date: Tue, 13 Jul 2004 12:06:53 -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: <20040713190653.GC8872@dhcp50.pn.xcllnt.net> In-Reply-To: <20040713210221.C547@korben.in.tern> References: <20040713203158.E548@korben.in.tern> <20040713190119.GB8872@dhcp50.pn.xcllnt.net> <20040713210221.C547@korben.in.tern>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 13, 2004 at 09:02:57PM +0200, Lukas Ertl wrote: > On Tue, 13 Jul 2004, Marcel Moolenaar wrote: > > >On Tue, Jul 13, 2004 at 08:33:34PM +0200, Lukas Ertl wrote: > >>Hi there, > >> > >>is the debug.debugger_on_panic sysctl supposed to work after the recent > >>DDB/KDB changes? I set it to 0, but I'm still thrown into DDB after > >>panic. > > > >Yes, the sysctl is still working as expected. > > Well, at least not on this box, or I'm completely misunderstanding > something. 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 :-) As a first: make sure you're not being dropped in the debugger for other reasons. If boot() appears in the backtrace, the sysctl works. -- 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?20040713190653.GC8872>