Subject: Re: kern/32665: kernel diagnostic assertion in uvm_fault.c
To: None <email@example.com>
From: Roland Dowdeswell <firstname.lastname@example.org>
Date: 01/30/2006 10:57:06
Is this reproduceable? If so, try to get a stack trace from the
process which is curproc. My DDB is a little rusty, but try a ps
and a tr/t. Then you'll be able to see what the curproc was trying
to do when the fault occurred. Make sure that you read the ddb(4)
man page about hex vs. decimal.
I think that the right answer is:
ddb> tr/t 0t33212
where 33212 is the decimal process id of the current proc.
Roland Dowdeswell http://www.Imrryr.ORG/~elric/