Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

version 5.00.2195.10 crashes on run-time breakpoint

OSR_Community_UserOSR_Community_User Member Posts: 110,217
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
---
You are currently subscribed to windbg as: xxxxx@interwoven.com
To unsubscribe send a blank email to $subst('Email.Unsub')

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    I have that problem with all the later releases of WinDbg. I currently have the
    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
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Developing Minifilters 29 July 2019 OSR Seminar Space
Writing WDF Drivers 23 Sept 2019 OSR Seminar Space
Kernel Debugging 21 Oct 2019 OSR Seminar Space
Internals & Software Drivers 18 Nov 2019 Dulles, VA