http://bugs.winehq.org/show_bug.cgi?id=58480
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org
--- Comment #4 from Bernhard Übelacker bernhardu@mailbox.org --- With lmms-1.3.0-alpha.1.862+4c3f819-linux-x86_64.AppImage I am able to receive a SIGSEGV at this instruction inside "Synth1 VST64.dll":
=> 0x6ffffc5e1a25 <s1vst!main+224789>: movss %xmm3,(%r9) (gdb) print/x $r9 $1 = 0xfeb8e9b0 (gdb) x/1xg $r9 0xfeb8e9b0: Cannot access memory at address 0xfeb8e9b0
With $r9 being 0xfeb8e9b0, seems no valid address because `cat /proc/$(pidof RemoteVstPlugin64.exe.so)/maps` shows no mapping at this address.
This is followed by a recursive SIGSEGV in RtlVirtualUnwind2. But I see this also with a build having 518e394794 reverted.
I tried also the windows nightly, to stay completely within wine boundaries, and this shows the same SIGSEGV. lmms-1.3.0-alpha.1.862+4c3f819-mingw-win64.exe. https://lmms.io/download/artifact/3481792904
=> 0x6fffe9451a25 <s1vst!main+224789>: movss %xmm3,(%r9) (gdb) print/x $r9 $1 = 0xfe9be1a0 (gdb) x/1xg $r9 0xfe9be1a0: Cannot access memory at address 0xfe9be1a0
`cat /proc/$(pidof 'C:\Program Files\LMMS\plugins\RemoteVstPlugin64.exe')/maps` shows again no mapping at this address.
This happens here also with 518e394794 reverted.
Running without attached gdb makes winedbg attach which shows a lengthy backtrace, but all in `synth1 vst64.dll` or remotevstplugin64.exe, without any debug information.