http://bugs.winehq.org/show_bug.cgi?id=58156
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org
--- Comment #7 from Bernhard Übelacker bernhardu@mailbox.org --- Created attachment 78553 --> http://bugs.winehq.org/attachment.cgi?id=78553 Working fine with wine-10.7 in Linux, smackw32 PROCESS_ATTACH.txt
Tried to reproduce this also inside a linux VM with wine-10.7, and could not observe this issue with smackw32.dll. So this might be something specific to MacOS.
(In reply to ToastyBug from comment #5)
01c4:trace:module:process_attach (L"smackw32.DLL",0012FD24) - START 01c4:trace:module:MODULE_InitDLL (00280000 L"smackw32.DLL",PROCESS_ATTACH,0012FD24) - CALL 01c4:trace:module:LdrGetDllFullName module 00000000, name 0012F960. (00280000,PROCESS_ATTACH,0012FD24) - RETURN 0
As far as I understand this PROCESS_ATTACH means the DllMain function from the dll gets executed. In my attempts I receive a "RETURN 1", in the failing ones "RETURN 0".
To get some insight what happens in this call to DllMain one could execute with +relay like this: WINEDEBUG=+module,+relay \ wine JKDEMO.EXE -windowgui \ >> $WINEPREFIX/drive_c/relay2.log 2>&1
This creates kind of huge files, please put the lines between "PROCESS_ATTACH...CALL" and "PROCESS_ATTACH...RETURN 0" into a file and attach it here. For comparison I attached that part from my succeeding test.