Valiantsin DzerakhandClaude Opus 5.5 869edd45cf Report crashes outside totk.exe instead of ending without a log line ...

A fault in a GPU driver, the C runtime or another DLL, or a call through a null pointer, ended the process with
nothing in totk.log: crash_veh reports only faults whose rip is in this executable (#506, #531, #488, #415).

Windows: an unhandled-exception filter reports every exception no handler took. It runs only after every handler
declined, so exceptions a driver raises and catches itself never reach it, and it costs nothing until a crash. The
report names the module (from its export directory, no loader lock) and the return addresses in totk.exe on the
faulting thread's stack, unwound from the faulting context.

Linux: fault_handler passes faults in libraries (Mesa, SDL) and at address 0 to the crash hook as well, with the
library name from dladdr.

--probe-crash-call (strlen in ucrtbase.dll reads address 8) and --probe-crash-null crash on purpose. Before: exit
0xc0000005 and no FATAL line. After: "FATAL: access violation ... (ucrtbase.dll+0xf2b61)" with host frames
probe_crash and main, exit 71.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-03 09:50:27 +03:00

..

common.c

Build and run the runtime natively on Linux.

2026-10-29 16:56:56 -03:00

fp_x86.h

Add the recompiler, Windows runtime, tools and docs

2026-10-23 22:27:54 +03:00

linux.c

Report crashes outside totk.exe instead of ending without a log line

2026-11-03 09:50:27 +03:00

platform.h

Report crashes outside totk.exe instead of ending without a log line

2026-11-03 09:50:27 +03:00

win32.c

Report crashes outside totk.exe instead of ending without a log line

2026-11-03 09:50:27 +03:00