Skip to content

Commit

Permalink
Don't signal an error for really early signals
Browse files Browse the repository at this point in the history
I'm getting annoyed about the repeated ABRT whenever there's some
early issue.
This also means that SIGWINCH and such won't cause an error and
halt a build.
  • Loading branch information
Bike committed Nov 13, 2024
1 parent 08d76c3 commit 618e70f
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions src/core/mpPackage.cc
Original file line number Diff line number Diff line change
Expand Up @@ -494,10 +494,11 @@ void posix_signal_interrupt(int sig) {
if (_sym_posix_interrupt->fboundp())
core::eval::funcall(_sym_posix_interrupt->symbolFunction(),
core::clasp_make_fixnum(sig));
else
core::cl__cerror(core::SimpleBaseString_O::make("Ignore signal"),
core::SimpleBaseString_O::make("Received POSIX signal ~d"),
core::Cons_O::createList(core::clasp_make_fixnum(sig)));
// If it's too early to call into Lisp, we do nothing
// and return. This makes it so that, for example, an ABRT signal
// will not be handled and thus terminate the process, rather than
// be "handled" so a few dozen ABRTs need to be sent to actually
// kill the process.
multipleValues.loadFromTemp(nvals, mv_temp);
}

Expand Down

0 comments on commit 618e70f

Please sign in to comment.