[Bug 47203] New: winedbg --gdb Game300.exe gives Internal crash at 0x7e9a06f9 (w3dhub/ecw)

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

Bug ID: 47203
           Summary: winedbg --gdb Game300.exe gives Internal crash at
                    0x7e9a06f9 (w3dhub/ecw)
           Product: Wine
           Version: 4.8
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: dbghelp
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 64458
  --> https://bugs.winehq.org/attachment.cgi?id=64458
dbghelp: Avoid crash in pe_load_msc_debug_info.

An interesting debugging topic got written to the forums in [1].

There a crash of "winedbg --gdb" got described that I could reproduce
which ends here:

Unhandled exception: page fault on read access to 0x017ac000 in 32-bit code
(0x7e9a06f9).
...
Backtrace:
=>0 0x7e9a06f9 pe_load_msc_debug_info+0xc3() [dlls/dbghelp/pe_module.c:597] in
dbghelp (0x0032e5a8)
  1 0x7e9a0ae8 pe_load_debug_info+0x67() [dlls/dbghelp/pe_module.c:715] in
dbghelp (0x0032e5d8)
  2 0x7e9a0d8f pe_load_native_module+0x23c() [dlls/dbghelp/pe_module.c:774] in
dbghelp (0x0032e838)
  3 0x7e991ff8 SymLoadModuleExW+0x2db(BaseOfDll=0x400000)
[dlls/dbghelp/module.c:643] in dbghelp (0x0032e8b8)
...

Attached patch contains a hack to check if the memory where parts of the
debug information is expected is mapped into the process.
And contains the full backtrace.

[1]
https://forum.winehq.org/viewtopic.php?f=2&t=32324&sid=001e48b2bd4f8...