https://bugs.winehq.org/show_bug.cgi?id=47972
Bug ID: 47972 Summary: Paraworld: segfaults at start Product: Wine Version: 4.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: ybyt4t@gmail.com Distribution: ---
On start I just get a crash with:
# wine C:/Program\ Files/Sunflowers/ParaWorld/bin/Paraworld.exe --- 0009:err:seh:setup_exception_record stack overflow 1040 bytes in thread 0009 eip 7bc6c30c esp 00230f20 stack 0x230000-0x231000-0x330000 ---
I did
--- setcap cap_net_bind_service=+eip /usr/bin/wine-preloader ---
before this, as suggested in #18014, which seemed to fix something, as otherwise it seems to crashes earlier into the debugger with:
--- (crash without setcap) --- wine: Unhandled page fault on write access to 0x00aceb99 at address 007075C0 (thread 0009), starting debugger... ---
Not sure about the Paraworld version, probably 1.0 (DVD version, box label ECD008134M). Distro: Arch (x86-64)
https://bugs.winehq.org/show_bug.cgi?id=47972
--- Comment #1 from ybyt4t@gmail.com ybyt4t@gmail.com --- Created attachment 65471 --> https://bugs.winehq.org/attachment.cgi?id=65471 start with WINEDEBUG=+relay,+seh,+tid
https://bugs.winehq.org/show_bug.cgi?id=47972
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
--- Comment #2 from Ken Sharp imwellcushtymelike@gmail.com --- Please attach the FULL console output without debug flags.
https://bugs.winehq.org/show_bug.cgi?id=47972
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to Ken Sharp from comment #2)
Please attach the FULL console output without debug flags.
Well, normally, yeah, but I don't think this'll tell us anything new.
The first crash is with STATUS_ILLEGAL_INSTRUCTION, which is certainly interesting. It's also hard to debug without knowing which instruction caused the crash. One would have to see disassembly around the faulting address (0x70448f).
https://bugs.winehq.org/show_bug.cgi?id=47972
--- Comment #4 from ybyt4t@gmail.com ybyt4t@gmail.com --- I can try to do the disassembly. Can you tell me, what is the best way to do that? Is it possible to generated a core dump or so?
https://bugs.winehq.org/show_bug.cgi?id=47972
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- (In reply to ybyt4t@gmail.com from comment #4)
I can try to do the disassembly. Can you tell me, what is the best way to do that? Is it possible to generated a core dump or so?
Ideally, static disassembly of the binary on disk. I prefer `objdump -d` for this. It might be obfuscated, though, which makes things significantly harder.
https://bugs.winehq.org/show_bug.cgi?id=47972
--- Comment #6 from ybyt4t@gmail.com ybyt4t@gmail.com --- Created attachment 65904 --> https://bugs.winehq.org/attachment.cgi?id=65904 backtrace of run with wine 4.21
https://bugs.winehq.org/show_bug.cgi?id=47972
--- Comment #7 from ybyt4t@gmail.com ybyt4t@gmail.com --- Tested it again, and unfortunately the behavior has changed after system upgrade. I'm on v4.21 now and it's messy to get back to 4.18 due to library dependencies. Thus I did a fresh install of Paraworld on wine 4.21.
It still crashes, though. Attached is the back trace.
https://bugs.winehq.org/show_bug.cgi?id=47972
--- Comment #8 from ybyt4t@gmail.com ybyt4t@gmail.com --- Created attachment 66416 --> https://bugs.winehq.org/attachment.cgi?id=66416 Crash with Wine 5.0
https://bugs.winehq.org/show_bug.cgi?id=47972
--- Comment #9 from ybyt4t@gmail.com ybyt4t@gmail.com --- Still wame problem with Wine 5.0
-
WineHQ Bugzilla