Is it just me, or is the latest WinDbg a bit buggier than the older ones? I
am using version 6.1.0017.0.
I keep getting this when I hit a breakpoint:
Unable to insert breakpoint 0 at bec5d532, NTSTATUS 0xC0000001
“{Operation Failed} The requested operation was unsuccessful.”
bp0 at bec5d532 failed
WaitForEvent failed
nt!DebugService+10:
80535082 8945fc mov [ebp-0x4],eax
Anyone know why? It prevents me from going on and I have to kill and
restart the debugger. Even then, it will do it again at the same point, so
I am forced to put a hardcoded breakpoint in my code once this happens.
Also, when I start WinDbg and it connects, it leaves the kd> command line
active even when the debugger has not broken in on the target. You can type
commands there and they executed when you really do break in. Just weird
not really a problem.
–
Bill McKenzie
Compuware Corporation
http://www.compuware.com/products/driverstudio/
“Bill McKenzie” wrote in message
news:xxxxx@windbg…
>
>
> Is it just me, or is the latest WinDbg a bit buggier than the older ones?
I
> am using version 6.1.0017.0.
Yes, it does seem like it has more bugs.
[snip]
> Anyone know why? It prevents me from going on and I have to kill and
> restart the debugger. Even then, it will do it again at the same point,
so
> I am forced to put a hardcoded breakpoint in my code once this happens.
I’ve seen that, I’ve worked around it by clearing all the breakpoints, then
adding them in again. My guess is that this is a fragile band-aid, but it
has worked for me so far.
[snip]
Phil
–
Philip D. Barila
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.
E-mail address is pointed at a domain squatter. Use reply-to instead.
Thanks, but it doesn’t work for me.
–
Bill McKenzie
Compuware Corporation
http://www.compuware.com/products/driverstudio/
“Phil Barila” wrote in message
news:xxxxx@windbg…
>
> “Bill McKenzie” wrote in message
> news:xxxxx@windbg…
> >
> >
> > Is it just me, or is the latest WinDbg a bit buggier than the older
ones?
> I
> > am using version 6.1.0017.0.
>
> Yes, it does seem like it has more bugs.
>
> [snip]
>
> > Anyone know why? It prevents me from going on and I have to kill and
> > restart the debugger. Even then, it will do it again at the same point,
> so
> > I am forced to put a hardcoded breakpoint in my code once this happens.
>
> I’ve seen that, I’ve worked around it by clearing all the breakpoints,
then
> adding them in again. My guess is that this is a fragile band-aid, but it
> has worked for me so far.
>
> [snip]
>
> Phil
> –
> Philip D. Barila
> Seagate Technology, LLC
> (720) 684-1842
> As if I need to say it: Not speaking for Seagate.
> E-mail address is pointed at a domain squatter. Use reply-to instead.
>
>
>
>
The clearing then enabling them again has usually worked for me but
there have been a couple of times where I had to set the breakpoints on
different lines than they were on before or I kept getting the same error.
-scott
“Bill McKenzie” wrote in message
news:xxxxx@windbg…
>
> Thanks, but it doesn’t work for me.
>
> –
> Bill McKenzie
> Compuware Corporation
> http://www.compuware.com/products/driverstudio/
>
>
>
> “Phil Barila” wrote in message
> news:xxxxx@windbg…
> >
> > “Bill McKenzie” wrote in message
> > news:xxxxx@windbg…
> > >
> > >
> > > Is it just me, or is the latest WinDbg a bit buggier than the older
> ones?
> > I
> > > am using version 6.1.0017.0.
> >
> > Yes, it does seem like it has more bugs.
> >
> > [snip]
> >
> > > Anyone know why? It prevents me from going on and I have to kill and
> > > restart the debugger. Even then, it will do it again at the same
point,
> > so
> > > I am forced to put a hardcoded breakpoint in my code once this
happens.
> >
> > I’ve seen that, I’ve worked around it by clearing all the breakpoints,
> then
> > adding them in again. My guess is that this is a fragile band-aid, but
it
> > has worked for me so far.
> >
> > [snip]
> >
> > Phil
> > –
> > Philip D. Barila
> > Seagate Technology, LLC
> > (720) 684-1842
> > As if I need to say it: Not speaking for Seagate.
> > E-mail address is pointed at a domain squatter. Use reply-to instead.
> >
> >
> >
> >
>
>
>
>
6.1.17.2 has fixed my problem and seems more stable.
“Doug” wrote in message news:xxxxx@windbg…
>
> Much buggier.
>
> Doug
>
>
>
>
I was too quick. 6.1.17.2 no longer displays the KD> prompt, but it still
says ‘Debuggee not connected’ even though it has connected. Still broke.
“Doug” wrote in message news:xxxxx@windbg…
>
> 6.1.17.2 has fixed my problem and seems more stable.
>
> “Doug” wrote in message news:xxxxx@windbg…
> >
> > Much buggier.
> >
> > Doug
> >
> >
> >
> >
>
>
>
>