Closed NetSysFire closed 2 months ago
New trace:
So I found out that it is mandatory to use --userdir ~/.local/share/cataclysm-dda/ --configdir ~/.config/cataclysm-dda/
to reproduce this corrupted path. I think its because of the length of the path.
The crash still happens without the args but when these args are used, it will reliably corrupt the path.
The user below had this crash path with a 4 char username, erus: �(���dus/.config/cataclysm-dda/crash.log
For reference, mine is 13 chars long, user12345name and the binary garbage that gets prepended to my path is longer.
So I found out that it is mandatory to use
--userdir ~/.local/share/cataclysm-dda/ --configdir ~/.config/cataclysm-dda/
to reproduce this. I think its because of the length of the path.
I was able to reproduce this just now, specifically by sending SIGTERM and using the above command line arguments.
Describe the bug
Luckily not too bad of a crash.
Attach save file
n/a
Steps to reproduce
handle_key_blocking_activity
. Waiting will probably work here, too.Expected behavior
No crash. I know that in some cases when you ctrl+c the game, which sends SIGINT instead of SIGTERM, there is a "really quit? want to save?" dialogue.
Screenshots
No response
Versions and configuration
Additional context
I can reliably reproduce the corrupted crash log thing with this!! #54886