Re: Testing random IOCTL calls
- From: "Doron Holan [MSFT]" <doronh@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 18 Aug 2008 14:38:39 -0700
1) enable the KMDF veriifer on your driver (use wdfverifier.exe in the 6001 WDK)
2) when you hit the breakpoint, dump the log for your driver (http://blogs.msdn.com/doronh/archive/2006/07/31/684531.aspx)
3) read the output. if you can't figure out, copy/paste it to your reply here
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chug100" <Chug100@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:A69D9B62-3590-47FB-85FA-A29E2B774821@xxxxxxxxxxxxxxxx
Hello,
I am working on a driver based upon the KMDF sample usbsamp. I am trying to
pass the DevPathExer tests and I have encountered a wierd set of cases.
I have created a handler for EvtIoDeviceControl and I have set it up so
every IoControlCode value is to return STATUS_INVALID_DEVICE_REQUEST with a
information field of zero indicating the number of bytes transferred. I then
call WdfCompleteRequestWithInformation.
In most cases this seems fine but there are a few IOCTL codes that produce:
Break instruction exception - code 80000003 (first chance)
nt!DbgBreakPoint:
fffff800`01026cd0 cc int 3
1: kd>
in the debugger.
The stack trace for this looks like:
nt!DbgBreakPoint
wdf01000!FxRequest::CompleteInternal+0x182
wdf01000!imp_WdfRequestCompleteWithInformation+0x12e
iwrstreo!WdfRequestCompleteWithInformation+0x2e
iwrstreo!UsbSamp_EvtIoDeviceControl+0x2a
wdf01000!FxIoQueue::DispatchRequestToDriver+0x6d9
wdf01000!FxIoQueue::DispatchEvents+0x83e
wdf01000!FxIoQueue::QueueRequest+0x4a6
wdf01000!FxPkgIo::Dispatch+0x718
wdf01000!FxDevice::Dispatch+0xa9
nt!IopXxxControlFile+0xa79
nt!NtDeviceIoControlFile+0x56
nt!KiSystemServiceCopyEnd+0x3
ntdll!NtDeviceIoControlFile+0xa
0x1`00020615
0x1`00000002
0x1
0x1`0005afd0
0x0
0x1`0005bb48
Needless to say I am baffled. I am not sure why some IOCTL codes are fine
and others are not.
.
- References:
- Testing random IOCTL calls
- From: Chug100
- Testing random IOCTL calls
- Prev by Date: Driver not signed by Microsoft messagebox appears multiple times
- Next by Date: Re: Driver not signed by Microsoft messagebox appears multiple times
- Previous by thread: Testing random IOCTL calls
- Next by thread: Driver not signed by Microsoft messagebox appears for EVERY device
- Index(es):
Relevant Pages
|
