[Bug 37200] Warhammer 40k: Kill Team (Steam version) does not start

[wine-bugs at winehq.org]

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

--- Comment #6 from Anastasius Focht <focht at gmx.net> ---
Hello Zentarim,

thanks for the trace.

--- quote ---
Can you recommend the name of the debugger with which I could get a trace?
--- quote ---

'winedbg' as registered just-in-time debugger/crash handler should be fine in
most cases.
Unfortunately another exception happens during fault handling which prevents
'winedbg' from being started here.

--- snip ---
...
0043:trace:process:create_process_impl app L"C:\\Program
Files\\Steam\\steamapps\\common\\W40K Kill Team\\killteam.exe" cmdline
L"\"C:\\Program Files\\Steam\\steamapps\\common\\W40K Kill Team\\killteam.exe\"
-nominidumps -nobreakpad -noassert -nocrashdialog"
...
0043:trace:process:create_process_impl started process pid 0054 tid 0055
...
0055:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x3bde078, format
DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x33f400, desc (nil) partial
stub!
0055:trace:seh:raise_exception code=c0000005 flags=0 addr=0x110025 ip=00110025
tid=0055
0055:trace:seh:raise_exception  info[0]=00000001
0055:trace:seh:raise_exception  info[1]=00000000
0055:trace:seh:raise_exception  eax=03bdae51 ebx=7dda9000 ecx=00000000
edx=03be10b0 esi=03bde078 edi=00000000
0055:trace:seh:raise_exception  ebp=0033f3c8 esp=0033f34c cs=0073 ds=007b
es=007b fs=0033 gs=003b flags=00210202
0055:trace:seh:call_stack_handlers calling handler at 0xc7d2e0 code=c0000005
flags=0
0055:trace:seh:call_stack_handlers handler at 0xc7d2e0 returned 1
0055:trace:seh:call_stack_handlers calling handler at 0xa743d8 code=c0000005
flags=0
...
wine: Unhandled page fault on write access to 0x00000000 at address 0x110025
(thread 0055), starting debugger...
0055:trace:seh:start_debugger Starting debugger "winedbg --auto 84 568"
0055:trace:process:create_process_impl app (null) cmdline L"winedbg --auto 84
568"
0055:trace:process:find_exe_file looking for L"winedbg"
0055:trace:process:find_exe_file Trying native exe
L"C:\\windows\\system32\\winedbg.exe"
0055:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7bc5099b
ip=7bc5099b tid=0055
0055:trace:seh:raise_exception  info[0]=00000001
0055:trace:seh:raise_exception  info[1]=00000004
0055:trace:seh:raise_exception  eax=00000000 ebx=7bcc7000 ecx=03be10e8
edx=03bdc360 esi=00000002 edi=000029a0
0055:trace:seh:raise_exception  ebp=0033e5f8 esp=0033e440 cs=0073 ds=007b
es=007b fs=0033 gs=003b flags=00210206
0055:trace:seh:call_stack_handlers calling handler at 0x7bc80220 code=c0000005
flags=0
...
0055:err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr
0x7bc5099b
0043:warn:debugstr:OutputDebugStringA "Game removed: AppID 275610 \"Warhammer
40,000: Kill Team\", ProcID 84 \n"
--- snip ---

You could try to run a few times without trace log (WINEDEBUG) but with the
proposed arguments, maybe the debugger can still attach upon first exception.
In that case save it to 'backtrace.txt'.

--- snip ---
WINEDEBUG=+tid,+seh,+loaddll,+process,+debugstr wine gdb ./steam.exe
--- snip ---

You probably meant 'winedbg' here.

Anyway, debugging Steam games is not for the faint-hearted.
I wouldn't recommend it unless you have the experience.

You either attach at the right point to the child or you need to go the way
with parent being debuggee and 'set $AlsoDebugProcChild=1' (which can be very
annoying/confusing if multiple child processes are spawned).

Regards

-- 
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.