RE: UMDF driver debugging

NTDEV
1

Hi,
I’m trying to debug my UMDF driver,
and while trying to attach the debugger (windbg -pn WUDFHost.exe),
I receive this message:
“Unable to find process “WUDFHost.exe”, HRESULT 0x80004002
No such interface supported”.
What am I doing wrong?
Thanks,
Gadi

2

It’s very possible your device isn’t ever getting started, or that the fault is occurring very early during device initialization and so you don’t have time to attach before the host exits.

Have you set the HostProcessDbgBreakOnStart registry value? Make it a reasonable value like 30 seconds (0x1e in hex) and you should have time after your device is attached to look for a host.

Also you probably need to run the debugger elevated on Vista since the host runs as a service process and not under your user account.

If you set this value and still can’t see a host show up then you should check setupapi.log (setupapi.dev.log on Vista) to see whether your device has installed correctly.

-p

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
Sent: Thursday, January 04, 2007 8:09 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] UMDF driver debugging

Hi,
I’m trying to debug my UMDF driver,
and while trying to attach the debugger (windbg -pn WUDFHost.exe),
I receive this message:
“Unable to find process “WUDFHost.exe”, HRESULT 0x80004002
No such interface supported”.
What am I doing wrong?
Thanks,
Gadi

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

Hi,
Thanks for the quick reply.
I have tried what you said, and still could not run the WinDbg.
in the setupapi.dev.log I get two types of errors.
The first is:

sig: Using catalog ‘C:\Windows\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT’.
! sig: VerifyTrustFailed for C:\Windows\system32\DRIVERS\UMDF\WUDFOsrUsbDriver.dll.
! sig: Error 87: The parameter is incorrect.
cpy: DrpSetRegFileProt ‘C:\Windows\system32\DRIVERS\UMDF\WUDFOsrUsbDriver.dll’ Status=0 Class=OEM Legacy
flq: File ‘C:\Windows\system32\WudfUpdate_01005.dll’ pruned from copy.
sig: Using catalog ‘C:\Windows\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT’.
! sig: VerifyTrustFailed for C:\Windows\system32\WudfUpdate_01005.dll.
! sig: Error 87: The parameter is incorrect.
cpy: DrpSetRegFileProt ‘C:\Windows\system32\WudfUpdate_01005.dll’ Status=0 Class=OEM Legacy
flq: File ‘C:\Windows\system32\WdfCoInstaller01005.dll’ pruned from copy.
sig: Using catalog ‘C:\Windows\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT’.
! sig: VerifyTrustFailed for C:\Windows\system32\WdfCoInstaller01005.dll.
! sig: Error 87: The parameter is incorrect.

and the second is:

dvi: Install Device: Restarting device. 00:10:27.584
dvi: Install Device: Restarting device completed. 00:11:04.162
!!! dvi: Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
and later:
ndv: Performing device install final cleanup…
! ndv: Queueing up error report since device has a PnP problem…

I don’t know if the first one is relevant at all, and if this is a problem in the inf file or in the code, but at the bottom line I think I cannot run the WinDbg because the device doesn’t start. But on the other hand I can’t debug because I still can’t run the windbg on it.
Any idea what am I doing wrong?
Thanks,
Gadi

4

An addition to my previous question -
If I try to attach the debugger before I get the “Device Cannot Start” yellow icon in the device manager, (the message there is still “No drivers are installed for this device”), the debugger attachment succeeds, and it stops in the “Break execution exception - first chance”, ntdll!DbgBreakPoint.
But when I try to put a breakpoint in the appropriate source file, I get a message which says that the “Symbol information for the current line could not be located in the currently loaded symbols”, even though it is the correct source file. Trying to reload it, I get another message “Code not found. breakpoint not set”.
I think all these issues are related to the device-start issue, and not to the debugger. Where should I look for the problem? In the inf? The code? Which methods are more likely to produce this issue?
(My code is actually the echo_driver in the UMDF samples, but because I don’t have an fx2 device, I have changed the inf and the source file to fit my device Hardware ID).
Thanks,
Gadi

5

See if “%windir%\setupact.log” contains any entries from the UMDF or KMDF coinstallers.

Also you’ll need to include the WinUSB coinstaller. If you search the archives for this mailing list you can find a recent conversation about how to add the WinUsbCoinstaller to your INF.

-p

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
Sent: Sunday, January 07, 2007 8:19 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] RE: UMDF driver debugging

Hi,
Thanks for the quick reply.
I have tried what you said, and still could not run the WinDbg.
in the setupapi.dev.log I get two types of errors.
The first is:

sig: Using catalog ‘C:\Windows\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT’.
! sig: VerifyTrustFailed for C:\Windows\system32\DRIVERS\UMDF\WUDFOsrUsbDriver.dll.
! sig: Error 87: The parameter is incorrect.
cpy: DrpSetRegFileProt ‘C:\Windows\system32\DRIVERS\UMDF\WUDFOsrUsbDriver.dll’ Status=0 Class=OEM Legacy
flq: File ‘C:\Windows\system32\WudfUpdate_01005.dll’ pruned from copy.
sig: Using catalog ‘C:\Windows\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT’.
! sig: VerifyTrustFailed for C:\Windows\system32\WudfUpdate_01005.dll.
! sig: Error 87: The parameter is incorrect.
cpy: DrpSetRegFileProt ‘C:\Windows\system32\WudfUpdate_01005.dll’ Status=0 Class=OEM Legacy
flq: File ‘C:\Windows\system32\WdfCoInstaller01005.dll’ pruned from copy.
sig: Using catalog ‘C:\Windows\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem4.CAT’.
! sig: VerifyTrustFailed for C:\Windows\system32\WdfCoInstaller01005.dll.
! sig: Error 87: The parameter is incorrect.

and the second is:

dvi: Install Device: Restarting device. 00:10:27.584
dvi: Install Device: Restarting device completed. 00:11:04.162
!!! dvi: Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
and later:
ndv: Performing device install final cleanup…
! ndv: Queueing up error report since device has a PnP problem…

I don’t know if the first one is relevant at all, and if this is a problem in the inf file or in the code, but at the bottom line I think I cannot run the WinDbg because the device doesn’t start. But on the other hand I can’t debug because I still can’t run the windbg on it.
Any idea what am I doing wrong?
Thanks,
Gadi

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

6

At that breakpoint your driver probably hasn’t been loaded yet. This breakpoint is for the host startup, not for any particular driver.

If your driver is named foo, do “bu foo!DllMain” or “bu foo!DllGetClassObject”. This will set a breakpoint which should get resolved once module “foo” is loaded. Then enter “g” to start the debugger.

You should get a breakpoint now at the entry point of your driver.

-p

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@n-trig.com
Sent: Monday, January 08, 2007 7:54 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] RE: UMDF driver debugging

An addition to my previous question -
If I try to attach the debugger before I get the “Device Cannot Start” yellow icon in the device manager, (the message there is still “No drivers are installed for this device”), the debugger attachment succeeds, and it stops in the “Break execution exception - first chance”, ntdll!DbgBreakPoint.
But when I try to put a breakpoint in the appropriate source file, I get a message which says that the “Symbol information for the current line could not be located in the currently loaded symbols”, even though it is the correct source file. Trying to reload it, I get another message “Code not found. breakpoint not set”.
I think all these issues are related to the device-start issue, and not to the debugger. Where should I look for the problem? In the inf? The code? Which methods are more likely to produce this issue?
(My code is actually the echo_driver in the UMDF samples, but because I don’t have an fx2 device, I have changed the inf and the source file to fit my device Hardware ID).
Thanks,
Gadi

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

7

And the information about getting the WinUSB co-installer for Windows XP
is not in the WDK documentation, but only in the “Release Notes”.
:slight_smile: (Yes, I fell into that trap.) -H

Peter Wieland schrieb:

See if “%windir%\setupact.log” contains any entries from the UMDF or KMDF coinstallers.

Also you’ll need to include the WinUSB coinstaller. If you search the archives for this mailing list you can find a recent conversation about how to add the WinUsbCoinstaller to your INF.

-p