Suspected gnutls issue, request help debugging

Questions about Wine on Linux
Post Reply
invisible kid
Level 1
Level 1
Posts: 7
Joined: Tue Dec 24, 2019 3:23 pm

Suspected gnutls issue, request help debugging

Post by invisible kid » Tue Dec 24, 2019 3:35 pm

I have a multilib LFS distro.
Windows solitaire and other apps work.
Blizzard apps that authenticate crash.
I've re-built and installed 32 bit libraries for gnutls, nettle and others.
I am looking for help debugging the issue.
Here is the back trace:
0060:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0060:fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x32f288
0060:fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x32f288
0060:fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3
0060:fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3
0060:fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
0060:fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
ecc-random.c:75: _nettle_ecc_mod_random: Assertion `nbytes <= m->size * sizeof (mp_limb_t)' failed.
wine: Assertion failed at address F7FC9B39 (thread 0054), starting debugger...
rom: ecc-random.c:75: _nettle_ecc_mod_random: Assertion `nbytes <= m->size * sizeof (mp_limb_t)' failed.
wine: Assertion failed at address F7F93B39 (thread 0060), starting debugger...
Unhandled exception: assertion failed in 32-bit code (0xf7f93b39).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:f7f93b39 ESP:0031a590 EBP:0031a5ac EFLAGS:00200286( - -- I S - -P- )
EAX:00000000 EBX:00000002 ECX:0031a5ac EDX:00000000
ESI:00000008 EDI:00000000
Stack dump:
0x0031a590: 0031a5ac 00000000 0031a5ac f7bce142
0x0031a5a0: 00000110 00000041 f7d797d8 00000000
0x0031a5b0: 00000000 00000100 7ced63b8 f7c1b605
0x0031a5c0: 00000110 00000080 f7c1b4b9 f757d000
0x0031a5d0: f7d797d8 00000080 00000000 f7d797d8
0x0031a5e0: 00000000 7cf160a8 f7d79000 7cf18b18
Backtrace:
=>0 0xf7f93b39 __kernel_vsyscall+0x9() in [vdso].so (0x0031a5ac)
1 0xf7bce142 int_mallinfo+0xffffffff() in libc.so.6 (0x0031a5ac)
2 0xf7bb82b6 int_mallinfo+0xffffffff() in libc.so.6 (0xf7d79ce0)
3 0xf7bb81c1 int_mallinfo+0xffffffff() in libc.so.6 (0xf7d79ce0)
4 0xf7bc62a9 int_mallinfo+0xffffffff() in libc.so.6 (0x7cf14c10)
5 0xf75901b8 ecc_sqrt_z+0xffffffff() in libhogweed.so.4 (0x7cf14c10)
6 0xf7590cad ecc_sqrt_z+0xffffffff() in libhogweed.so.4 (0x0031a9b8)
7 0xf79ebcb8 _wrap_nettle_pk_sign+0x18f7() in libgnutls.so.30 (0x0031aa18)
8 0xf79c119f _wrap_nettle_pk_sign+0xffffffff() in libgnutls.so.30 (0x7cf08030)
9 0xf79c13ce _wrap_nettle_pk_sign+0xffffffff() in libgnutls.so.30 (0x0031ab20)
10 0xf7921aab _wrap_nettle_pk_sign+0xffffffff() in libgnutls.so.30 (0x0031ab20)
11 0xf791c4db _wrap_nettle_pk_sign+0xffffffff() in libgnutls.so.30 (0x00000000)
12 0xf7b519d2 schan_imp_handshake+0x11() [Z:\usr\src\wine-4.19\wine32-build\dlls\secur32\..\..\..\dlls\secur32\schannel_gnutls.c:327] in secur32 (0x0031abb8)
13 0xf7b4f7f8 schan_InitializeSecurityContextW+0x197(phCredential=<couldn't compute location>, phContext=<couldn't compute location>, pszTargetName=<couldn't compute location>, fContextReq=<couldn't compute location>, Reserved1=<couldn't compute location>, TargetDataRep=<couldn't compute location>, pInput=<couldn't compute location>, Reserved2=<couldn't compute location>, phNewContext=<couldn't compute location>, pOutput=<couldn't compute location>, pfContextAttr=<couldn't compute location>, ptsExpiry=<couldn't compute location>) [Z:\usr\src\wine-4.19\wine32-build\dlls\secur32\..\..\..\dlls\secur32\schannel.c:896] in secur32 (0x0031ac08)
14 0xf7b5880b InitializeSecurityContextW+0x1ca(phCredential=<couldn't compute location>, phContext=<couldn't compute location>, pszTargetName=<couldn't compute location>, fContextReq=<couldn't compute location>, Reserved1=<couldn't compute location>, TargetDataRep=<couldn't compute location>, pInput=<couldn't compute location>, Reserved2=<couldn't compute location>, phNewContext=<couldn't compute location>, pOutput=<couldn't compute location>, pfContextAttr=<couldn't compute location>, ptsExpiry=<couldn't compute location>) [Z:\usr\src\wine-4.19\wine32-build\dlls\secur32\..\..\..\dlls\secur32\wrapper.c:345] in secur32 (0x0031aca8)
15 0x0042eecb EntryPoint+0xffffffff() in blizzarderror (0x0031ad54)
16 0x0042fdd5 EntryPoint+0xffffffff() in blizzarderror (0x0031ad74)
17 0x0042fef6 EntryPoint+0xffffffff() in blizzarderror (0x0031ad8c)
18 0x0041f3a5 EntryPoint+0xffffffff() in blizzarderror (0x0031adac)
19 0x004434c3 EntryPoint+0xffffffff() in blizzarderror (0x0031adc4)
20 0x00420dad EntryPoint+0xffffffff() in blizzarderror (0x0031add4)
21 0x004281dd EntryPoint+0xffffffff() in blizzarderror (0x0031ae14)
22 0x00428ac4 EntryPoint+0xffffffff() in blizzarderror (0x0031ae44)
23 0x0041cf7e EntryPoint+0xffffffff() in blizzarderror (0x0031ae70)
24 0x0041d078 EntryPoint+0xffffffff() in blizzarderror (0x0031ae84)
25 0x0041d09e EntryPoint+0xffffffff() in blizzarderror (0x0031ae94)
26 0x0040bedf EntryPoint+0xffffffff() in blizzarderror (0x0031aeb4)
27 0x0040b928 EntryPoint+0xffffffff() in blizzarderror (0x0032f448)
28 0x00402d47 EntryPoint+0xffffffff() in blizzarderror (0x0032f5c0)
29 0x00415020 EntryPoint+0xffffffff() in blizzarderror (0x0032fe90)
30 0x0046dbe3 EntryPoint+0xffffffff() in blizzarderror (0x0032ff20)
31 0x7b466199 call_process_entry+0x18() in kernel32 (0x0032ff48)
32 0x7b46a04f start_process+0x11e(entry=<couldn't compute location>, peb=<couldn't compute location>) [Z:\usr\src\wine-4.19\wine32-build\dlls\kernel32\..\..\..\dlls\kernel32\process.c:1029] in kernel32 (0x0032ffd8)
33 0x7b4661aa start_process_wrapper+0x9() in kernel32 (0x0032ffec)
0xf7f93b39 __kernel_vsyscall+0x9 in [vdso].so: popl %ebp

Thank you very much for any help anyone can offer!

invisible kid
Level 1
Level 1
Posts: 7
Joined: Tue Dec 24, 2019 3:23 pm

Re: Suspected gnutls issue, request help debugging

Post by invisible kid » Sat Jan 04, 2020 6:53 am

Solved. I don't believe these errors were causing my main issue. After fixing another issue, I was able to successfully launch a couple Blizzard apps, and I think I still get these errors in the logs. But since it is generally working, I am no longer concerned about them at the moment.

invisible kid
Level 1
Level 1
Posts: 7
Joined: Tue Dec 24, 2019 3:23 pm

Re: Suspected gnutls issue, request help debugging

Post by invisible kid » Sun Jan 05, 2020 6:39 am

For posterity and anyone finding this when searching for their issue I think changing Windows version from 7 to 10 fixed whatever problem I was having here.

invisible kid
Level 1
Level 1
Posts: 7
Joined: Tue Dec 24, 2019 3:23 pm

Re: Suspected gnutls issue, request help debugging

Post by invisible kid » Sun Jan 05, 2020 7:58 am

Might still be an issue. I am able to login for wow launching its 64 bit client directly, but maybe my 32 bit builds of gnutls/nettle are still problematic. Maybe try building any packages that assemble with ASFLAGS=--32.

Post Reply