[ros-kernel] Crashes...

[Mike Nordell]

Hartmut Birr wrote:

> > yes, insert a MessageBox in the __except clause in
> > BaseProcessStart() on  line 377 of that file.
>
> Please do it not. If ROS runs in text mode, each user mode fault
> will start the gui.

Another thing that crossed my mind is - what about "According to Redmond
Logic, press Cancel to debug or OK to kill it"? Is it really recommended to
try to start the debugger to attach to the current process from within an
exception handler of the crashing thread (which might already have corrupted
so much memory)? When running CUI-mode (initially, and currently), perhaps a
CUI "dialog" should pop up with the same text, to allow the user to enter
GUI-mode and debug, or at least inspect from a debugger, the crashing
process/thread?

Since the behaviour in NT is dependent on a few registry settings (not only
what debugger to run with what params, but also if it even should display
the dialog), is it really good to put this (amount of conditional) code into
ntdll? Another thing is that if we look at e.g. NT5+ there is an Information
entry written to the System log with the contents of that popup dialog (*).
Is every process then going to need write access to the System log?

(*) This text is (about?) the same as you get when pressing CTRL+Ins/CTRL+C
in a dialog in NT5+, i.e. the text from the dialog and its buttons.

Taking these and other details into account, I'm currently leaning towards
not having this code in ntdll.

/Mike