Article 5AB0T Wine-5.18 page fault

Wine-5.18 page fault

by
business_kid
from LinuxQuestions.org on (#5AB0T)
I'm getting a fairly repeatable crash from wine on the 'back' button of a library program. There was an option to save a backtrace which I did. It's a long harmless enough output after the first bit Code:Unhandled exception: page fault on read access to 0x00010248 in 32-bit code (0x6ccdb84d).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:6ccdb84d ESP:0031f55c EBP:0031f634 EFLAGS:00210206( R- -- I - -P- )
EAX:00010244 EBX:0db93640 ECX:00000001 EDX:000102fc
ESI:0031f5e0 EDI:0031f5c0
Stack dump:
0x0031f55c: 000102fc 00000111 00008012 00070190
0x0031f56c: 00000000 00430769 00000000 0031f6ac
0x0031f57c: 00070190 00020104 0dbbc520 00000000
0x0031f58c: 00000000 000f000b 00000000 00000000
0x0031f59c: 0031f5cc 6eda836c 00070190 00000001
0x0031f5ac: 0000000b 0000000f 00070190 0000e800
Backtrace:That looks an awful lot like a segfault, which indicates poor software. Last night I had this recurring 100% of the time in one instance, while hardly at all in another. The program itself has been pretty stable for years, and is probably compiles for an i386sx or something very low level like that. Wine is 5.18-staging from Alien Bob. The kernel is 5.4.68-generic.

The only thought that strikes me is that we're 32bit here, in that it thinks it's a '386 and the database is over 4G, even the ext4 disk is 64bit. Does anyone know for sure if that stuff is safely handled?latest?d=yIl2AUoC8zA latest?i=hIh_EW_w1bw:FipevvBb3Lk:F7zBnMy latest?i=hIh_EW_w1bw:FipevvBb3Lk:V_sGLiP latest?d=qj6IDK7rITs latest?i=hIh_EW_w1bw:FipevvBb3Lk:gIN9vFwhIh_EW_w1bw
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments