The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
RE: LolClient.exe crash in libcrypto.so.1.0.0 / ssleay_rand_add+0x30c()
by Amos Wenger on Sunday April 10th 2011, 11:34
I have compiled Wine with GnuTLS (just cleaned and reconfigured with ./configure --with-gnutls and rebuilt just to be sure), so it's not that.
I have libcrypto 1.0.0 and 0.9.8 installed, /usr/lib/libcrypto.so was a symlink to /usr/lib/libcrypto.so.1.0.0 but I have tried changing it to libcrypto.so.0.9.8 and it still crashes all the same.
Note that I only had the info that it crashed in libcrypto when launching LolClient.exe manually - so maybe it's completely unrelated to the actual crash when launched by lol.launcher.exe
The only info I have when running lol.launcher.exe is
wine: Unhandled page fault on read access to 0xffffffff at address 0x7c78eeac (thread 003e), starting debugger...
Except it never starts the debugger, or at least I'm not able to see it, because then I could get a backtrace which would be useful..
When starting lol.launcher.exe with winedbg, it crashes all the same, but then when I try to type "bt" in the terminal it types nothing. If I hit Ctrl+C it displays "Ctrl-C: stopping debuggee" and then I can type bt and I get a stakctrace in lol.launcher, GetMessageW, wait_message, X11DRV_MsgWaitForMultipleObjectsEx, NtWaitForMultipleObjects, NTDLL_wait_for_multiple_objects, wait_reply, __libc_read, __kernel_vsyscall so.. I don't see the relation with libcrypto
I also see messages like:
err:wininet:HTTP_HttpOpenRequestW Unable to escape String!(insert URL-like string here)
and a lot of fixme:wininet and fixme:hnetcfg.
Here's a complete log, surprisingly including a complete backtrace (when run with wine lol.launcher.exe 2>&1 tee &> /tmp/log.txt): bpaste.net/show/15314/