kennykerr
commented
1 year ago @mikebattista A simple way to smoke out these types, both in win32 and wdk metadata, is to look for structs that don't have any fields. There are quite a few across both the Win32 and WDK metadata and this could be used to quickly weed out invalid struct definitions in both repos. They're not always handle types but they're almost always an indicator of some invalid struct scraping. Here are just a few that are obviously wrong:
Windows.Win32.Data.HtmlHelp.IITGroup- should be an interface, although I can't find the definitionWindows.Win32.Devices.BiometricFramework._WINIBIO_ENGINE_CONTEXT- should be a typedef/handle calledPWINIBIO_SENSOR_CONTEXTthat contains avoid*
Searching for structs with zero fields will quickly bring them all in view.
mikebattista
Further testing revealed some invalid handle types that make certain APIs inexpressible. I'm not too familiar with the WDK but it seems that all or some of these underscore-prefixed structs should be handles:
For example: https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/nf-wdm-ioinitializeworkitem
Here the parameter is named
PIO_WORKITEMand this typedef should be a pointer to an opaque structure defined by the driver. I would expect it to be defined something like this:And then the empty
_IO_WORKITEMstruct should be removed. I assume many of the other underscore-prefixed structs fall into the same category, but again I'm not that familiar with the WDK.