Re: ddb(4) spoils kernel stack in CURRENT?
- From: Dmitry Pryanishnikov <dmitry@xxxxxxxxxxxxxx>
- Date: Wed, 20 Dec 2006 13:18:39 +0200 (EET)
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@xxxxxxxxxxxxxx
nic-hdl: LYNX-RIPE
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: ddb(4) spoils kernel stack in CURRENT?
- From: Kostik Belousov
- Re: ddb(4) spoils kernel stack in CURRENT?
- References:
- ddb(4) spoils kernel stack in CURRENT?
- From: Dmitry Pryanishnikov
- ddb(4) spoils kernel stack in CURRENT?
- Prev by Date: packets duplicated *massively* on transmit.
- Next by Date: A stuck system
- Previous by thread: ddb(4) spoils kernel stack in CURRENT?
- Next by thread: Re: ddb(4) spoils kernel stack in CURRENT?
- Index(es):
Relevant Pages
|
|