Suggestion: Interactive Kernel debugger?

[cb88]

The BSOD as can be often seen when people post their crashes from ReactOS or even MS windows.... isn't that useful.

It would be a deviation from how NT is usually interacted with however, highly useful as anyone that has ever helped debug a crash on Haiku OS can vouch for... especially as more real hardware is tested. It can also greatly accelerate the progress that is made on developing an OS because it highlights the bugs for the developers to work on that they missed on the first pass etc...

It's way more useful for an inexperienced user to post back to you a backtrace, or syslog then just a blind error ENUM etc..

[binarymaster]

This is what Debug (Screen) option for.

[hbelusca]

Otherwise one can use MSVC builds together with WinDbg, but otherwise yes, ReactOS (Debug) is the way. The only problem concerns the fact that the display is not readjusted when one quits the debugger.

[cb88]

This is what Debug (Screen) option for.

Ah, that does look similar (TAB+k) enters it... I did try it out but ended up corrupting my VM as it wouldn't boot thereafter. Haiku's KDL as they call it you can enter and exit pretty much at will without too many side effects. Also Haiku has their KDL infrastructure enabled by default.

[oldman]

What about using com0com or tty0tty with your VM.

[middings]

Is the original poster's question answered on the ReactOS Wiki's Debugging page?