[Bug 49286] New: Melodyne 5 crashes due to unimplimented WS2_32.dll.GetHostNameW

WineHQ Bugzilla wine-bugs at winehq.org
Thu May 28 19:19:48 CDT 2020


https://bugs.winehq.org/show_bug.cgi?id=49286

            Bug ID: 49286
           Summary: Melodyne 5 crashes due to unimplimented
                    WS2_32.dll.GetHostNameW
           Product: Wine-staging
           Version: 5.9
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: ToxicBugzilla at outlook.com
                CC: leslie_alistair at hotmail.com, z.figura12 at gmail.com
      Distribution: ---

Created attachment 67291
  --> https://bugs.winehq.org/attachment.cgi?id=67291
The backtrace.

Installed Melodyne 5 trial
(https://services.celemony.com/cgi-bin/WebObjects/LicenseApp.woa/wa/demoRegistration?item=Melodyne5-Demo-Win&language=en)
with mfc42, vcrun6, and vcrun2019 installed in a 64 bit prefix due to Melodyne
5 only working in 64 bit now. (installer will crash without it due to missing
dll contained, plus Melodyne 5 needs vcrun2019 from my research) Installer
works fine, (b47a56f747bf3a477f2a564ee65eb005d40e6ef7 setup.exe)
 but launching the resulting Melodyne.exe
(e9b21aa11efbbc01d76df17ee4e7a421c2186986 [sha1 of Melodyne.exe could vary due
to unique installs on every computer? unsure, but setup.exe should stay the
same) itself will give this in the terminal:

002c:fixme:winediag:__wine_start_process Wine Staging 5.8 is a testing version
containing experimental patches.
002c:fixme:winediag:__wine_start_process Please mention your exact version when
filing bug reports on winehq.org.
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:ole:CoInitializeSecurity
(0000000000000000,-1,0000000000000000,0000000000000000,0,3,0000000000000000,0,0000000000000000)
- stub!
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsprintf_s options 24 not handled
00c0:fixme:msvcrt:MSVCRT__stdio_common_vsnprintf_s options 24 not handled
00c0:fixme:ntdll:NtQuerySystemInformation info_class
SYSTEM_PERFORMANCE_INFORMATION
wine: Call from 0x7bc8b9ac to unimplemented function WS2_32.dll.GetHostNameW,
aborting
wine: Unimplemented function WS2_32.dll.GetHostNameW called at address
000000007BC8B9AC (thread 00c0), starting debugger...

Due to being unable to find any mention of it anywhere except for Microsoft's
website noting of its addition, this is probably a bug in normal Wine &
development as well, but I have yet to test due to time constraints.
Also, when opening "show details" in the debugger,
"00c8:fixme:dbghelp:elf_search_auxv can't find symbol in module" get spammed in
the terminal excessively. (62 times)

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list