[Bug 49556] New: 0024:err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc88e20

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49556

            Bug ID: 49556
           Summary: 0024:err:seh:raise_exception Unhandled exception code
                    c0000005 flags 0 addr 0x7bc88e20
           Product: Wine-staging
           Version: 5.12
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: kenorb at gmail.com
                CC: leslie_alistair at hotmail.com, z.figura12 at gmail.com
      Distribution: ---

I'm using filever.exe inside Docker container which in some configuration
crashes on run, and some works.

Initially I've managed to make it not crash with:
- wine-5.9 (Staging)
- wine-5.12 (Staging)

But after using wine-5.12 a while, I couldn't make it not crash.

When running: wine filever.exe terminal64.exe
it works fine.

When running: wine filever.exe /v terminal64.exe
it shows the following output and crashes:

--a-- W32    APP   -      5.0.0.2515 shp 56,960,616 07-03-2020 terminal64.exe
    Language    0x0000 (English)
    CharSet        0x04b0 Unicode
...
    SubType:    00000000
    FileDate:    00000000:00000000
wine: Unhandled page fault on read access to 65786526 at address 7BC88E20
(thread 0024), starting debugger...
0024:err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr
0x7bc88e20


$ winedbg filever.exe /v terminal64.exe
007c:err:ntoskrnl:ZwLoadDriver failed to create driver
L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142
WineDbg starting on pid 00c8
0x000000007bcd18a5: ret
Wine-dbg>bt
Backtrace:
=>0 0x000000007bcd18a5 (0x000000000031ffd8)
  1 0x000000007b449622 EntryPoint+0x23651() in kernel32 (0x000000000031ffec)
Wine-dbg>bt all
0x000000007bcd18a5: ret
Backtracing for thread 00cc in process 00c8 (C:\windows\filever.exe):
Backtrace:
=>0 0x000000007bcd18a5 (0x000000000031ffd8)
  1 0x000000007b449622 EntryPoint+0x23651() in kernel32 (0x000000000031ffec)
0x000000007bcd18a5: ret

Here are the reproducible steps using Docker container (which I'm using):

1. Pull and run Docker container:

local$ docker run -it --entrypoint /bin/bash ea31337/ea-tester

2. Inside Docker, install required binaries (e.g. filever and platform binary
to check).

docker$ /opt/scripts/eval.sh install_mt 5.0.0.2515

3. Go to downloaded platform dir.

$ cd ~/.wine/drive_c/MetaTrader\ 5/

4. This command should work:

$ wine filever.exe terminal64.exe
--a-- W32    APP   -      5.0.0.2515 shp 56,960,616 07-03-2020 terminal64.exe

5. This command crashes at the end:

$ wine filever.exe /v terminal64.exe
...
    FileDate:    00000000:00000000
wine: Unhandled page fault on read access to 65786526 at address 7BC88E20
(thread 0024), starting debugger...
0024:err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr
0x7bc88e20

6. Although works for another binaries:

$ wine filever.exe /v metatester64.exe
(no errors at the end)
$ wine filever.exe /v metaeditor64.exe
(no errors at the end)

7. To run under debugger, run:

$ winedbg filever.exe /v terminal64.exe

Xvfb is already running, run: "export DISPLAY=:0" to access display.

The filever.exe is the same which is included with
WindowsXP-KB838079-SupportTools
(https://github.com/EA31337/EA-Tester/releases/download/4.x/WindowsXP-KB838079-SupportTools-ENU.exe).
If you download from the link, you can use cabextract to extract that binary
(e.g. cabextract -F support.cab *.exe && cabextract -F filever.exe *.cab &&
install -v filever.exe ~/.wine/drive_c/windows).

I was using filever.exe quiet often in my scripts and never had this issue.

Any clues if that's the Wine bug or filever.exe?

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.