On Wed, Dec 20, 2006 at 01:18:39PM +0200, Dmitry Pryanishnikov wrote: > > 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). Could you further localize the problem, i.e. try to backtrace CURRENT dump by RELENG_6 kgdb and vice versa.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:04 UTC