https://github.com/ohrrpgce/ohrrpgce/commit/1ddc0be5dd072a853bfd8414c006893e3f664260
Author: teeemcee <teeemcee@7d344553-34f0-0310-a9b1-970ce8f1c3a2>
Date: Wed Aug 13 15:56:07 2025 +0000
SIGTERM/SIGINT now quit cleanly (and SIGQUIT terminates) instead of calling
fatalerror
I saw a video of Digital Soul Data running on a Linux-based handheld (which
I
can't identify, but there's quite a few of them) where pressing the power
button
sends SIGTERM, which caused a very ugly FATAL error message.
Specifically SIGTERM/SIGINT set closerequest, and SIGQUIT prints a stack
trace
(like other signals) and then calls fatal_error_shutdown. Other error
signals
(including calling abort()) still call fatalbug.
common.rbas | 2 +-
common_base.bas | 14 ++++++++++++--
common_base.bi | 2 ++
custom.bas | 2 +-
errorlog.h | 2 +-
gfx.bi | 5 +++--
miscc.c | 2 +-
os_unix.c | 29 ++++++++++++++++++-----------
util.bas | 21 +++++++++++++++------
util.bi | 2 +-
whatsnew.txt | 2 ++
yetmore2.bas | 2 +-
12 files changed, 58 insertions(+), 27 deletions(-)
_______________________________________________
Ohrrpgce mailing list
[email protected]
http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
