https://bugs.winehq.org/show_bug.cgi?id=47174
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to Louis Lenders from comment #2)
Created attachment 64451 [details] last 3500 lines before the failure of loading the dll
For info I attach last 3500 lines before the (not present) dll fails to load
I don`t know if it has anything to do with the bug but just before the dll fails to load there`s:
002a:Call KERNEL32.RaiseException(406d1388,00000000,00000006,0024f980) ret=1401860d7 002a:trace:seh:NtRaiseException code=406d1388 flags=0 addr=0x7b456156 ip=7b456156 tid=002a
That seems to have to do with naming a thread, was also referenced in bug https://bugs.winehq.org/show_bug.cgi?id=25243 . Is this something that works in wine? Also mentioned for example in https://blogs.msdn.microsoft.com/stevejs/2005/12/20/naming-threads-in-win32- and-net/
(As I said, don`t know if this is the cause, might be red herring)
That's a red herring; it's completely opaque to the application whether naming the thread actually does anything or not (and notably I'm pretty sure it only does something when running under a debugger).
If the library is failing to load, the interesting part is probably what happens inside of LoadLibrary(). What failure code is it returning? What does a +module trace say?