http://bugs.winehq.org/show_bug.cgi?id=20351
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #7 from Anastasius Focht focht@gmx.net 2009-10-15 11:03:17 --- Hello,
I remember encountering such strange symptoms before.
When new Windows API functions are added to Wine dlls (just like HeapQueryInformation stub), the order of exports (and ordinals) naturally changes (if not explicitly specified). JIT compiled .NET assemblies (MSIL compiled to native code) have various optimizations also related to imports of unmanaged API. Basically due to API exports reordering, the wrong function is resolved/called from native image, leading to such strange symptoms.
You might try to force recreation of your NGEN cache (native .NET images) in WINEPREFIX and try your app again.
Something like this:
1. remove "c:\windows\assembly\NativeImages_xxx" folder just to be sure no leftover. 2. run 'wine ./ngen.exe update' (from where ngen.exe resides) 3. run your app
AFAIK when Windows Updates service updates system binaries, ngen is automatically scheduled, taking care of invalidated native .NET images.
Regards