Date: Wed, 25 Jan 2012 16:53:42 +0100 From: Michiel Boland <boland37@xs4all.nl> To: freebsd-sparc64@freebsd.org Subject: Re: Howto debug Kernel problems ? (jail -r -> freeze) Message-ID: <4F202586.5010808@xs4all.nl> In-Reply-To: <926170B2-9DF2-4DCC-9643-E66E6504B185@4lin.net> References: <5C638638-3D1A-417E-A574-9BCE51E08C59@4lin.net> <20120124202111.GB7731@alchemy.franken.de> <431CCA8C-2E5E-43BC-89EE-7F06CF8E8E8D@4lin.net> <20120125150054.GA15762@alchemy.franken.de> <926170B2-9DF2-4DCC-9643-E66E6504B185@4lin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/25/2012 16:09, Denny Schierz wrote: > > Am 25.01.2012 um 16:00 schrieb Marius Strobl: >> >> Not that I'm aware of. Do you have a kernel built with options >> BREAK_TO_DEBUGGER? Does it work when the machine doesn't hang > > jupp, I have > >> (you can resume via the "continue" command in the kernel > > works too > >> debugger)? Do you send the break via the "break" command of the >> ALOM or by sending a break via a terminal attached to the ALOM >> console? > > > ssh alom -> login -> type break -> type console -f -> normal freebsd console > > but, It happens nothing. I expected to get into the kdb. > > cu denny What happens if you do # sysctl debug.kdb.alt_break_to_debugger=1 then type the alternate break sequence (Enter ~ ^B) on the console?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F202586.5010808>