Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Upcoming OSR Seminars | ||
---|---|---|
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
Internals & Software Drivers | 19-23 June 2023 | Live, Online |
Writing WDF Drivers | 10-14 July 2023 | Live, Online |
Kernel Debugging | 16-20 October 2023 | Live, Online |
Developing Minifilters | 13-17 November 2023 | Live, Online |
Comments
older NT4 WinDbg installed as well so that I can use one flavor for NT4 and the
other for W2K.
If you find out why let me know. :-)
Thanks
Mike
Subject: [windbg] version 5.00.2195.10 crashes on run-time breakpoint
Hi all,
has anyone seen this behaviour with setting run-time enabled breakpoints?
Every time I set a breakpoint, using the F9 key, in my driver
code, I run and upon hitting the line with the breakpoint,
windbg crashes silently. By silently, I mean just disappears on
my host development machine. I have to start it again and enable
all the options (kernel debugging, symbol path etc) then run.
Windbg is at the correct point in the code and the target is stopped
at this point. All is correct, however, it is VERY annoying to have
to keep restarting Windbg and reloading every time I set and hit
a breakpoint.
I am running NT 4 Sp5 on my development machine running Windbg with the
latest SDK installed. Target machine being debugged is NT 4 Sp4 and
NT 4 Sp5. Same situation happens with both targets.
Thanks
Steve