Repository navigation
FatalProgramException: return its message from message() - #1841
Merged
Mysticial merged 1 commit intoNov 4, 2026
Merged
Conversation
It kept the message but never overrode Exception::message(), so readers got an empty string: the fatal-error notification and logs that print name() + ": " + message() showed "FatalProgramException: " alone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AKYzhrMnPK61XHWEch4a6E
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
FatalProgramExceptionstores its message but never overridesException::message(), so the log line, the error box and the fatal-error notification all show just "FatalProgramException" with no reason. This adds the one-line override, the same asOperationFailedExceptionhas.Built on macOS. On a Switch, a program that stopped with a
FatalProgramExceptionnow logs the reason instead of an empty message.