Skip to content

docs: add BugSplat_IsWerEnabled to the Windows C API reference - #326

Merged
bobbyg603 merged 1 commit into
masterfrom
docs/c-api-is-wer-enabled
Aug 27, 2026
Merged

docs: add BugSplat_IsWerEnabled to the Windows C API reference#326
bobbyg603 merged 1 commit into
masterfrom
docs/c-api-is-wer-enabled

Conversation

@bobbyg603

Copy link
Copy Markdown
Member

Summary

Documents BugSplat_IsWerEnabled, added in bugsplat-windows#162.

The C++ IsWerEnabled() method was already in the reference, but the C API had no equivalent — so P/Invoke and C consumers had no way to tell whether the WER path was armed. That matters because WER registration fails silently when BugSplatWer.dll isn't beside the executable or the RuntimeExceptionHelperModules value is missing, and what's lost is exactly the crashes nothing else can catch: stack buffer overrun, heap corruption, and __fastfail.

The entry links to the existing Registry Changes section rather than repeating the setup.

Merge timing

Hold until bugsplat-windows#162 ships in a release, so the documented export exists in the SDK customers can download. It's queued for the next one.

🤖 Generated with Claude Code

The C++ class method IsWerEnabled was already documented, but the C API had no
equivalent until bugsplat-windows#162 added one. Without it, P/Invoke and C
consumers had no way to tell whether the WER path was armed.

Notes what is lost when it returns 0, since WER registration fails silently when
BugSplatWer.dll is missing or the registry value is absent.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@bobbyg603
bobbyg603 merged commit 1661a91 into master Aug 27, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants