http://bugs.winehq.org/show_bug.cgi?id=6880
------- Additional Comments From focht@gmx.net 2007-05-05 15:23 ------- Hello,
--- quote --- The solution you proposing won't work - there are some ... other protection systems that are not using GetProcAddress at all. Instead they muck around the export / import tables themselves. --- quote ---
Names? Are they *ever* supposed to work on wine? I bet the number of targets is very limited. To cope this braindamaged i-have-my-own-GetProcAddress stuff, the loader could hot-patch the export tables after mapping the dll into memory (cancelling out exports which are not supported by current plaform).
Though even this can be circumvented by directly reading the library into memory as "blob" (without LoadLibrary). I seriously doubt the value of supporting such type of software (e.g. malware).
--- quote --- So hiding anything in GetProcAddress might not work. Worse it can brake something. --- quote ---
It's exhibiting same behaviour like windows version. If an export doesnt exist on specific target platform, GetProcAddress() returns NULL.
Same problem domain for early bound (static) imports. The windows loader wont load dependency (module) with missing import (wrong platform) - while the wine loader happily does (which is IMHO wrong behaviour leading to problems).
Regards