Tracy's error handling overrides dotnet's

[amylizzle]

A null deref while Tracy is attached causes the whole program to exit and Tracy to report a crash. Normally the program would handle the null deref gracefully using a try/catch, but Tracy's error catching seems to override it. We have encountered a similar issue previously with Chromium Embedded Framework which was fixed by passing --disable-in-process-stack-traces as an argument in it's init proc.

Reproduction steps:

1. Have a C# program with Tracy attached through Tracy-CSharp (great project, thanks so much!)
2. intentionally trigger a null dereference in a try/catch loop

try {
    MyObject thing;
    thing.MyProc() //null deref
} catch (Exception e) {
    //handled gracefully
}

3. Tracy reports a crash, the debugged program exits with code 0.

System info: Linux x64 - Ubuntu 24.10, X11 window manager, dotnet 8, Tracy/Tracy-CSharp version 0.11.1