Subject: Re: kern/32665: kernel diagnostic assertion in uvm_fault.c
To: None <yamt@netbsd.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,>
From: Roland Dowdeswell <elric@imrryr.org>
List: netbsd-bugs
Date: 01/30/2006 16:55:02
The following reply was made to PR kern/32665; it has been noted by GNATS.

From: Roland Dowdeswell <elric@imrryr.org>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: kern/32665: kernel diagnostic assertion in uvm_fault.c 
Date: Mon, 30 Jan 2006 10:57:06 -0500

 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> ps
 	<examine output>
 	ddb> tr/t 0t33212
 
 where 33212 is the decimal process id of the current proc.
 
 Thanks,
 
 --
     Roland Dowdeswell                      http://www.Imrryr.ORG/~elric/