winspool.drv name aliasing with winspool.dll

[janbbeck]

Using the same file and methodology as #153
I get

APID[TRACE]: API Lookup: WINSPOOL:DocumentPropertiesW
APID[WHERE]: JSON API database /usr/local/share/pharos/apidb/pharos-api-additions.json has no data for DLL: WINSPOOL
APID[WHERE]: SQLite API database /usr/local/share/pharos/apidb/pharos-apidb.sqlite has no data for DLL: WINSPOOL
APID[WHERE]: Decorated name parser has no data for DLL: WINSPOOL
APID[WARN ]: API database has no data for DLL: WINSPOOL
OOAN[WARN ]: No stack delta information for: WINSPOOL.DRV:DocumentPropertiesW

This is very interesting. There is a file for winspool.dll in share/contrib which defines this and other missing names.

After some looking around, it appears that the very same file is sometimes called winspool.drv and at other times winspool.dll
https://answers.microsoft.com/en-us/windows/forum/windows_xp-performance/winspooldll-issue/89594fcf-ed04-4b16-bc93-9fbdbbdf4884

so should the name parser check for .dll definitions when finding .drv imports, or should some definitions be added replacing

"dll": "winspool.dll",

with

"dll": "winspool.drv",

?

[sei-gwassermann]

Interestingly we've already run into this problem of searching for winspool.drv but I suspect the information was added to the database as winspool.dll only. Will check.

[janbbeck]

No need to check. It is exactly as you say, at least for the winspool in share/contrib

[sei-gwassermann]

I believe it should be in the database and the share/contrib entry is unnecessary, will look into it.

[sei-eschwartz]

@sei-gwassermann Ping