# fix: Linux logs crashes with a backtrace · clo/snowbound

[View on GitCafe](https://git.cafe/clo/snowbound/commit/a19933d46506ade819b3ceb6e7d68fd97f13b832)

Repository: [clo/snowbound](https://git.cafe/clo/snowbound)

Visibility: public

Requested revision: a19933d46506ade819b3ceb6e7d68fd97f13b832

Requested commit: a19933d46506ade819b3ceb6e7d68fd97f13b832

Commit: a19933d46506ade819b3ceb6e7d68fd97f13b832

Tree: 45e864ce8943b8bf22210ef155fb51d98651563b

Author: clover caruso

Committer: clover caruso

## Message

```
fix: Linux logs crashes with a backtrace

Panics and the signals that end the process (SIGSEGV, SIGBUS, SIGILL,
SIGFPE, SIGABRT) now write a backtrace, with each frame's module and
offset, to $XDG_STATE_HOME/snowbound/snowbound.log (the last run's kept
as snowbound.old.log) and say where the log is. Where stderr reaches no
one, as when the desktop starts the app, stderr goes to the log as well,
as it does on Windows. The signal then ends the process as before, so
systemd-coredump still records it.

Assisted-by: claude-opus-5.5

```

## Parents

- [dd5848fb96853a2c144af246475587ad09f1aefa](https://git.cafe/clo/snowbound/commit/dd5848fb96853a2c144af246475587ad09f1aefa?format=markdown)

[Source at this commit](https://git.cafe/clo/snowbound/tree/a19933d46506ade819b3ceb6e7d68fd97f13b832?format=markdown)