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/