> If this is a "can't happen" kind of condition, rather than a
> temporary debugging aid, you should probably call panic() instead,
> since that will work whether or not DDB is compiled in, and will
> cause the right thing to happen either way (panic/crash dump for
> post-mortem, or dropping into the debugger).

This brings up a question: if panic() drops into ddb, is there any way
(short of really ugly hacks like bashing return addresses on the stack)
to "ignore" the panic, to cause panic() to simply return?

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B