On Wed, Apr 11, 2012 at 11:58, Stepa Nick <hired...@gmail.com> wrote: >> Run with `WINEDEBUG=loaddll wine my.exe` and ensure that builtin gdiplus >> is being used. > > > I run `WINEDEBUG=loaddll wine my.exe` and get such output: > >> trace:loaddll:load_builtin_dll Loaded L"KERNEL32.dll" at 0x7b810000: >> builtin >> trace:loaddll:load_native_dll Loaded >> L"Z:\\home\\user\\tmp\\test\\CalculateCPP.exe" at 0x400000: native >> trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" >> at 0x72540000: builtin >> trace:loaddll:load_builtin_dll Loaded >> L"C:\\windows\\system32\\advapi32.dll" at 0x68550000: builtin >> trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\gdi32.dll" >> at 0x684b0000: builtin >> trace:loaddll:load_builtin_dll Loaded >> L"C:\\windows\\system32\\version.dll" at 0x6e960000: builtin >> trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\user32.dll" >> at 0x68380000: builtin >> trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" >> at 0x70d00000: builtin >> trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\ole32.dll" >> at 0x685c0000: builtin >> trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\gdiplus.dll" >> at 0x4ec50000: native >> trace:loaddll:load_native_dll Loaded >> L"C:\\windows\\system32\\MSVCR100.dll" at 0x78aa0000: native >> trace:loaddll:load_builtin_dll Loaded >> L"C:\\windows\\system32\\shlwapi.dll" at 0x686c0000: builtin >> trace:loaddll:load_builtin_dll Loaded >> L"C:\\windows\\system32\\comctl32.dll" at 0x68720000: builtin >> trace:loaddll:load_builtin_dll Loaded >> L"C:\\windows\\system32\\msimg32.dll" at 0x68810000: builtin >> trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\mfc100u.dll" >> at 0x785f0000: native >> trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\imm32.dll" >> at 0x68bc0000: builtin >> trace:loaddll:load_builtin_dll Loaded >> L"C:\\windows\\system32\\winex11.drv" at 0x68980000: builtin >> trace:loaddll:load_builtin_dll Loaded >> L"C:\\windows\\system32\\uxtheme.dll" at 0x68c10000: builtin >> trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\dwmapi.dll" >> at 0x68c40000: builtin >> trace:loaddll:load_native_dll Loaded >> L"C:\\windows\\system32\\MFC100ENU.DLL" at 0x5d360000: native >> fixme:heap:HeapSetInformation (nil) 1 (nil) 0 >> fixme:win:EnumDisplayDevicesW ((null),0,0x32f744,0x00000000), stub! > > So, non-native gdiplus.dll used?! Hmm... Can I see into gdiplus.dll anyway? > I really need to understand how pixeloffset works.
We don't really encourage tracing native dlls, that could be interpreted as reverse engineering. You can force builtin gdiplus in winecfg, for what it's worth. I suppose gdi32 could also be at play, though I can't say that for sure. -- -Austin
