Override Native Crash Reporter for Windows

[bobbyg603]

Unity's crash reporter is basically useless. Let's override this with bugsplat-windows.

[bobbyg603]

Windows Native Crash Reporting - Implementation Plan

Background

The BugSplat Windows C++ SDK (BugSplat.lib) uses native Windows exception handling + WER (not Crashpad/Breakpad). It ships as a static library, which can't be loaded dynamically at runtime like the macOS dylib approach. For Unity integration, we need a wrapper DLL that exposes the same API as C exports.

Wrapper DLL (BugSplatDll)

Created source files in the bugsplat-windows repo at BugSplatDll/:

• BugSplatDll.h — C header with extern "C" __declspec(dllexport) for every BugSplat class method
• BugSplatDll.cpp — Thin forwarding layer using a global BugSplat* singleton

The DLL exposes functions like:

BugSplatDll_Init(database, appName, appVersion)
BugSplatDll_SetUser(user)
BugSplatDll_SetEmail(email)
BugSplatDll_SetAttribute(name, value)
BugSplatDll_SetNotes(notes)
BugSplatDll_PostAllCrashesAsync()
BugSplatDll_AddAttachment(filepath)
BugSplatDll_PostFeedback(title, description)
// ... full 1:1 mapping of the BugSplat C++ API

Visual Studio Setup

1. Add a new DLL project to BugSplatSDKs.sln
2. Add include path to BugSplat\inc
3. Define BUGSPLATDLL_EXPORTS preprocessor macro
4. Link against BugSplat.lib (or add project reference to BugSplatNative)
5. Build for x64 Release (and ARM64 if needed)

Unity Integration

Once BugSplatDll.dll is built, the Unity side needs:

1. Native plugins in Runtime/Plugins/Windows/x86_64/:

   • BugSplatDll.dll (our wrapper)
   • BugSplatMonitor.exe (crash upload handler)
   • BugSplatRc.dll (UI resources)
   • BugSplatWer.dll (WER integration)

2. C# P/Invoke bridge in BugSplat.cs:

   • [DllImport("BugSplatDll")] declarations
   • UNITY_STANDALONE_WIN && !UNITY_EDITOR platform path
   • Same SetNativeAttribute/SetNativeUser/etc. pattern as iOS/macOS

3. PostBuild to copy runtime dependencies to build output

4. Existing Windows minidump flow (PostAllCrashes/PostMostRecentCrash) can be removed once native reporting is active

Notes

• WER integration requires admin privileges to register BugSplatWer.dll in the registry — may need to document this as optional
• The SetGlobalCRTExceptionBehavior() and SetPerThreadCRTExceptionBehavior() helpers catch CRT exceptions (terminate, pure virtual, invalid parameter, SIGABRT) — important for comprehensive coverage
• Unlike macOS, the Windows SDK doesn't conflict with Unity's crash reporter since Unity uses its own UnityCrashHandler64.exe process on Windows, not a PLCrashReporter-style in-process handler