Save crash logs #52

New Issue

claunia · 2026-01-29T16:08:25Z

claunia commented

2026-01-29 16:08:25 +00:00

Originally created by @mnadareski on GitHub (Jun 25, 2018).

Originally assigned to: @mnadareski on GitHub.

Currently, if the program crashes, there is no way of determining what went wrong exactly. Implement a to-file logger that will write out in the event of an issue.

Possibly put one giant try-catch around the main app runtime?

Originally created by @mnadareski on GitHub (Jun 25, 2018). Originally assigned to: @mnadareski on GitHub. Currently, if the program crashes, there is no way of determining what went wrong exactly. Implement a to-file logger that will write out in the event of an issue. Possibly put one giant try-catch around the main app runtime?

claunia added the enhancement label 2026-01-29 16:08:25 +00:00

claunia closed this issue

2026-01-29 16:08:25 +00:00

claunia commented

2026-01-29 16:08:26 +00:00

@mnadareski commented on GitHub (Jan 28, 2020):

Hardening each of the internal parts of the code has proven to be more effective so far compared to having top-level exceptions logged. Nearly all places where there used to be issues have been addressed. I'm closing this for now, given that eventually, this would be good to have as part of the external logs.

@mnadareski commented on GitHub (Jan 28, 2020): Hardening each of the internal parts of the code has proven to be more effective so far compared to having top-level exceptions logged. Nearly all places where there used to be issues have been addressed. I'm closing this for now, given that eventually, this would be good to have as part of the external logs.

claunia referenced this issue

2026-01-29 16:24:24 +00:00

[PR #58] [MERGED] Formats and Types #938

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#52