There’s got to be an easy way to do this… getting _DRIVER_OBJECTs from a
crash dump using WinDbg>Actually I’ve never used the !new !improved windbag
to debug an NT4
system. Sorry to hear that it keeps crashing. Maybe the Microsoft support
It works FINE for me on NT4SP6 host and NT4-no-SPs target. It picks my
symbols OK, all commands are OK, breakpoints are OK.
The only annoying thing is that when it misses a symbol file (for ntdll.dll,
for instance) - it freezes for ~10 seconds while loading symbols.
Another minor problem is inability to show the nested block’s local
variables in the Locals window - only the largest function block variables
are shown.
Max