Question on breakpoint failure

Hello.

Sometimes when I surprise my stream class USB driver in Win2k SP3 or
WinXP SP1, I cannot set breakpoints in WinDBG after I replug the device. I
get such an error:

Unable to insert breakpoint 3 at f52c4d30, NTSTATUS 0xC0000001
“{Operation Failed} The requested operation was unsuccessful.”
bp3 at f52c4d30 failed
WaitForEvent failed
nt!RtlpBreakWithStatusInstruction+1:
805103fb c20400 ret 0x4

Has anyone seen similar errors? Am I corrupting memory? When I try to use
Driver Verifier, I sometimes get BSODs within stream.sys (bug check 0xC9,
param=6 : IRP completed with STATUS_PENDING or -1), but never yet in my
driver. Needless to say, I never myself complete an SRB with status
STATUS_PENDING or -1.

Could anyone shed any light on this matter? Thanks in advance.

Philip Lukidis

I’ve been getting similar problems when I unload my driver and then reload
it without previously clearing the breakpoints I had previously set. If I
clear the breakpoints (bc *) after getting this message everything appears
to work. I can even clear the old breakpoints and reset them before
continuing and everything is fine.

  • Steve -

-----Original Message-----
From: Philip Lukidis [mailto:xxxxx@hotmail.com]
Sent: Thursday, April 17, 2003 5:29 PM
To: NT Developers Interest List
Subject: [ntdev] Question on breakpoint failure

Hello.

Sometimes when I surprise my stream class USB driver in Win2k SP3 or
WinXP SP1, I cannot set breakpoints in WinDBG after I replug
the device. I
get such an error:

Unable to insert breakpoint 3 at f52c4d30, NTSTATUS 0xC0000001
“{Operation Failed} The requested operation was unsuccessful.”
bp3 at f52c4d30 failed
WaitForEvent failed
nt!RtlpBreakWithStatusInstruction+1:
805103fb c20400 ret 0x4

Has anyone seen similar errors? Am I corrupting memory?
When I try to use
Driver Verifier, I sometimes get BSODs within stream.sys (bug
check 0xC9,
param=6 : IRP completed with STATUS_PENDING or -1), but never
yet in my
driver. Needless to say, I never myself complete an SRB with status
STATUS_PENDING or -1.

Could anyone shed any light on this matter? Thanks in advance.

Philip Lukidis


You are currently subscribed to ntdev as: xxxxx@cognex.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Great, I’ll give that a shot when I resume testing. I hope that workaround
would apply to my case.

Thanks,

Philip Lukidis
----- Original Message -----
From: “Whitman, Steve”
To: “NT Developers Interest List”
Sent: Thursday, April 17, 2003 5:54 PM
Subject: [ntdev] RE: Question on breakpoint failure

> I’ve been getting similar problems when I unload my driver and then reload
> it without previously clearing the breakpoints I had previously set. If I
> clear the breakpoints (bc *) after getting this message everything appears
> to work. I can even clear the old breakpoints and reset them before
> continuing and everything is fine.
>
> - Steve -
>
> > -----Original Message-----
> > From: Philip Lukidis [mailto:xxxxx@hotmail.com]
> > Sent: Thursday, April 17, 2003 5:29 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Question on breakpoint failure
> >
> >
> > Hello.
> >
> > Sometimes when I surprise my stream class USB driver in Win2k SP3 or
> > WinXP SP1, I cannot set breakpoints in WinDBG after I replug
> > the device. I
> > get such an error:
> >
> > Unable to insert breakpoint 3 at f52c4d30, NTSTATUS 0xC0000001
> > “{Operation Failed} The requested operation was unsuccessful.”
> > bp3 at f52c4d30 failed
> > WaitForEvent failed
> > nt!RtlpBreakWithStatusInstruction+1:
> > 805103fb c20400 ret 0x4
> >
> > Has anyone seen similar errors? Am I corrupting memory?
> > When I try to use
> > Driver Verifier, I sometimes get BSODs within stream.sys (bug
> > check 0xC9,
> > param=6 : IRP completed with STATUS_PENDING or -1), but never
> > yet in my
> > driver. Needless to say, I never myself complete an SRB with status
> > STATUS_PENDING or -1.
> >
> > Could anyone shed any light on this matter? Thanks in advance.
> >
> > Philip Lukidis
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@cognex.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@hotmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

I’ve come to roughly the same conclusion. See my post in
microsoft.public.windbg on 2003-03-17 under “Oddity in.”


If replying by e-mail, please remove “nospam.” from the address.

James Antognini