http://bugs.winehq.org/show_bug.cgi?id=58364
--- Comment #4 from Michael Setzer II mikes@kuentos.guam.net --- Two additional comments. Created a Clean Install of Fedora 42 in a VirtualBox setup. ran dnf update get all default updates. Installed winehq-devel (10.10) Install went with no problem. Copied the PMAIL directory from live machine to Virtual ran WINPM-32.EXE Opens fine put image is again screw up. Not right layout and folders not showing. Closed program dnf downgrade winehq-devel to (10.9) ran WINPM-32.EXE and it displays just fine. So, not clear on how it can be something other the 10.10 that is the issue??
2nd comment. Wine is well outside my knowledge base. Had tried the WINEDEBUG options, and found that notepad would run with +heap added. Also, ran with strace, and seems to be that heap.c in ntdll on line 775 is where it has close line that seems to basically say if +heap option is set to just ignore the c0000005 error??
So, was just looking for options to isolate problem. Download the git and did configure and build, but running gives message that wine is a 64bit version, but the wine server is 32bit? But only wine is the git virsion. Perhaps a problem with using Fedora versus an apt based linux.
I started with computers in the mid 70s, with and IBM 1130 with 4K Ram, Punch cards, and 5M removable disk. So working with computers a long time. Taught computer science for 36 years.
Did have a couple issues of debugging come to mind. Had a UUCICO gateway I created for the old DOS version of Pegasus back in 90s. Worked fine for my college and other places around the world. Then had a close high school that had setup a sister relation ship with a High School in Isle of White (England) and we being on Guam. They only had 1 computer with modem on Novell network. So sending and receiving was one person at time. With Pegasus and Gateway any computer could create emails in queue and gateway would downlaod emails for each users private novell mail directory. Very simple setup. Gave him the files and simple instructions, but after he tried it didn't work?? I went to the high school, and it turned out to be a Dump error on my part. Didn't know that all there workstations were IBM System I machines, Novell server was a COMPAQ 386. On my system I had compiled program using +O2 option which had compiler using 80286 instructions, but the IBM System I machines had 8086 processors. So simple fix was to recompile without +O2 option, and then everything worked fine.
2nd option that came to miine was a 45 Page long program that had worked perfectly on our AS/400 for 8 years, and then started getting in a loop. Took me 8 hours to isolate exactly what line caused problem. Was an indicator (flag) that didn't get turned off under 1 exact situation that hadn't occurred in 8 years. Under normal operations, the COMPARE statement would reset that Indicator is if wasn't a match on first loop cycle, and process everything, but if first cycle was a match, loop. Fix was simple to Turn off indicator before loop cycle. So, debugging can be a process.
On other lists have seen issues with some programs having issues that they try to use CPU features that don't exist on all CPUs. Don't know if this is issing with latest winehq-devel. One notebook is a Aspire E1-731 (VAG70_HC_0685_2.29) with Pentium Dual Core CPU That one had issue with seh error with notepad, but worked with +heap. One with Pegasus Problem with 10.10 is Dell Lattitude 5580 with i7 cpu and 8 cores.
So, why 10.9 works, but 10.10 fails with no other changes. To me that seems to say that something between 10.9 and 10.10 is causing the problem??