> panic() no longer works when called early. E.g., after booting with -d,
> typing `panic<newline>' at the debugger prompt produces no output and
> hangs.
>
> This may be because panic() now depends on uninitialized event handlers.
That would only be an issue if panic() then calls boot() without
initialising it. Until boot() has been told how to restart the
particular hardware it's running on in an appropriate fashion, it's
somewhat difficult to do this "right".
Perhaps exit() needs to be implemented?
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\ -- Joseph Merrick \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
