1
1

signals: don't trap segfault/abort when envvar NANO_NOCATCH is defined

When the user wants to get a backtrace, the crash handler shouldn't
kick in.
Этот коммит содержится в:
Benno Schulenberg 2018-05-06 16:46:41 +02:00
родитель e889c28a95
Коммит c0b15c2982
2 изменённых файлов: 6 добавлений и 0 удалений

Просмотреть файл

@ -309,6 +309,10 @@ not by default distinguish modified from unmodified arrow keys.
Please report any other bugs that you encounter via:
.br
\fIhttps://savannah.gnu.org/bugs/?group=nano\fR.
.sp
When nano crashes, it will save any modified buffers to emergency .save files.
If you are able to reproduce the crash and you want to get a backtrace, define
the environment variable \fBNANO_NOCATCH\fR.
.SH HOMEPAGE
\fIhttps://nano-editor.org/\fR

Просмотреть файл

@ -1213,6 +1213,7 @@ void signal_init(void)
}
#ifndef DEBUG
if (getenv("NANO_NOCATCH") == NULL) {
/* Trap SIGSEGV and SIGABRT to save any changed buffers and reset
* the terminal to a usable state. Reset these handlers to their
* defaults as soon as their signal fires. */
@ -1220,6 +1221,7 @@ void signal_init(void)
act.sa_flags |= SA_RESETHAND;
sigaction(SIGSEGV, &act, NULL);
sigaction(SIGABRT, &act, NULL);
}
#endif
}