https://bugs.winehq.org/show_bug.cgi?id=45357
Bug ID: 45357 Summary: Proprietary program using solidframework libraries crashing (works in Windows) Product: Wine Version: 3.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: s.jegen@gmail.com Distribution: ---
Created attachment 61656 --> https://bugs.winehq.org/attachment.cgi?id=61656 Backtrace shown in the debug window
We have a proprietary (sadly) program, "solid-program", which uses the proprietary Solidframework PDF libraries that crashes after seeming to work for a while. An earlier version of the same program worked in Wine but activating OCR functionality (which makes it use more libraries I assume) makes it crash. Running the same "solid-program" on Windows 10 works without issues.
Attached are the backtrace (no function names. Not even for the (small) "solid-program" binary for which I have the source) and the debugging output with the +relay option.
The exception seems to come from some bogus value being read in the proprietary library. I cannot figure out why the proprietary library ends up reading that value in Wine but not in Windows.
I tried to run winedbg with "solid-framework" but I don't get any output:
$ winedbg /opt/solid-program/solid-program.exe -t docx -p "" test-files/simple-text.pdf WineDbg starting on pid 006b 0x000000007bc969f5 DbgBreakPoint+0x1 in ntdll: ret Wine-dbg>c 006c:fixme:kernelbase:AppPolicyGetProcessTerminationMethod 0xfffffffffffffffa, 0x23fbd0 Process of pid=006b has terminated
I tried to attach to the program (while the crash window is showing) but I get an error 5 (permission denied?):
Wine-dbg>info proc pid threads executable (all id:s are in hex) 0000007d 1 'winedbg.exe' 00000074 1 'solid-program.exe' 00000076 1 _ 'winedbg.exe' 00000078 4 _ 'explorer.exe' 00000037 1 'winedbg.exe' 0000000e 5 'services.exe' 0000002a 4 _ 'winedevice.exe' 00000025 3 _ 'plugplay.exe' 0000001d 4 _ 'winedevice.exe' Wine-dbg>attach 0x00000074 Can't attach process 0074: error 5
Any ideas?