version 5.00.2195.10 crashes on run-time breakpoint

WINDBG
1

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’)

2

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. :slight_smile:

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