Date: Wed, 20 Dec 2006 13:18:39 +0200 (EET) From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: freebsd-current@freebsd.org Subject: Re: ddb(4) spoils kernel stack in CURRENT? Message-ID: <20061220130559.P54963@atlantis.atlantis.dp.ua> In-Reply-To: <20061219175917.L84683@atlantis.atlantis.dp.ua> References: <20061219175917.L84683@atlantis.atlantis.dp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! On Tue, 19 Dec 2006, Dmitry Pryanishnikov wrote: > I've tried to repeat this under the RELENG_6 as of 30-Oct (just removing > kernel options COMPAT_43TTY, COMPAT_FREEBSD6, INVARIANTS, INVARIANT_SUPPORT, > and using 'debug.kdb.enter' instead of 'debug.kdb.panic') - and kgdb unwinds > the stack even if the dump got via typing 'panic' from ddb: Today I've tried this with the fresh (20-Dec) RELENG_6 and with INVARIANTS* (so the only difference between kernel configs are CURRENT-only options COMPAT_43TTY and COMPAT_FREEBSD6). No differences - kgdb successfully unwinds the stack under RELENG_6. It seems that the following stands: > So it looks like a regression in CURRENT vs RELENG_6 (either ddb 'spoils' the > stack somehow, or kgdb fails to unwind it). Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061220130559.P54963>