TUI for inspecting crash reports

[mitchellh]

#2173 was merged, which now generates crash reports.

It'd be nice if there was a Ghostty CLI that showed a TUI for inspecting the crash reports. This way users can be confident in what they contain before sending them to the project with a bug report. The crash reports are based on a publicly documented format and I already started a decoder so it shouldn't be too hard to bring this in.

I should note that our crash reports also likely contain a minidump (binary) formatted crash dump from Breakpad. Decoding this format would be nice one day but is a much larger task and out of scope for what I was imagining to close this issue.

My current thinking is that we'd expose this via ghostty +crash-report. I like smaller PRs so I recommend breaking this down into various stages (not in any specific order)

• List available crash reports (ghostty +crash-report with no args)
• Inspect a single crash report (ghostty +crash-report <path> or selecting one from the list)
• Deleting crash reports

There is more we can do but this would be nice to work on.

[mitchellh]

I will add: if you want to test crash reporting, #2173 introduced a keybinding you can use to generate a crash in a specific thread, the crash binding. Example:

keybind=x=crash:main
keybind=x=crash:render
keybind=x=crash:io

And remember, crash reports are generated on the next start of Ghostty. During an active crash, the crash capture just dumps the information it needs to generate the crash report the next time it runs.

[jcollie]

I've got a super basic start on the +crash-report action in #2184. All it does for now is just list available crash reports.

[mitchellh]

#2203 lays a lot of groundwork to make this easier, adds decoding structured types from an envelope and also reserialization if we ever implement modification.

[furtidev]

I was taking a look at #2184 and I think a TUI will work well for tty output too. I'm imagining simple navigation, choosing a report opens it up in the inspector. So, I guess the crash report inspector should be implemented first. I might take a look.