> - the shell32 exports many functions by ordinal withou a name.
> Your tool likely can't cope with it - or it would need to use *.dbg
> and *.pdb files to get symboles from. (have not tryed it jet)
It can cope with it - or at least it emits a symbol constructed from the name
of the DLL and the
> However, I've noticed that it doesn't appear to correlate with the already
> existing shell32.spec file based on a dump of the WinNT4 shell32.dll (at least
> as far as ordinals go). Can anyone explain this?
No, the shell32.spec is not based on any dump of a native shell32.dll.
- the shell32 ex
Since no-one out there seems to have one, I've written a small perl script
that reads the output of "objdump -x" run on a windows DLL and turns it into a
.spec file with all the function stubbed out (handy when you want to deal with
a DLL with over a thousand entry points).
However, I've noticed
