nethack-gwaa-kiwi/nethack
1
0
Fork 0
Code Pull Requests Activity

signal induced panictrace under curses

Browse Source 
When panictrace feedback occurs due to catching a signal rather
than controlled panic, the backtrace is useless when running the
curses interface unless the terminal gets reset first.  Let's
just hope that the signal triggering a panictrace doesn't occur
while resetting the terminal.
This commit is contained in:
PatR
2021-03-09 07:45:58 -08:00
parent 554297dd4a
commit cc855d6973
4 changed files with 38 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
win/curses/cursmain.c
View File

@@ -299,6 +299,19 @@ curses_get_nh_event(void)
}
}
/* restore terminal state; extracted from curses_exit_nhwindows() */
void
curses_uncurse_terminal(void)
{
/* also called by panictrace_handler(), a signal handler, so somewhat
iffy in that situation; but without this, newlines behave as raw
line feeds so subseqent backtrace gets scrawled all over the screen
and is nearly useless */
curses_cleanup();
curs_set(orig_cursor);
endwin();
}
/* Exits the window system. This should dismiss all windows,
except the "window" used for raw_print(). str is printed if possible.
*/
@@ -311,9 +324,8 @@ curses_exit_nhwindows(const char *str)
curses_destroy_nhwindow(MESSAGE_WIN);
curs_destroy_all_wins();
curses_cleanup();
curs_set(orig_cursor);
endwin();
curses_uncurse_terminal();
iflags.window_inited = 0;
if (str != NULL) {
raw_print(str);