From owner-freebsd-current Sun Apr 19 04:45:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09514 for freebsd-current-outgoing; Sun, 19 Apr 1998 04:45:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09506 for ; Sun, 19 Apr 1998 11:45:17 GMT (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA00099; Sun, 19 Apr 1998 21:43:30 +1000 Date: Sun, 19 Apr 1998 21:43:30 +1000 From: Bruce Evans Message-Id: <199804191143.VAA00099@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In <199803131513.CAA27634@godzilla.zeta.org.au>, Bruce Evans wrote: >> SIGQUIT handling is still buggy. For the simple Makefile: >> --- >> foo: >> sleep 1000 >> --- >> killing make with SIGQUIT gives the following behaviours: >> >> 1. make: exits with status 3 (SIGQUIT) (per the above change). >> 2. make -j4: hangs (broken). >> 3: gmake: exits with status 1. >> 3: gmake -j4: exits with status 1. >> >> POSIX.2 only requires a nonzero exit status for SIGQUIT. We've just >> fixed the handling of SIGINT, SIGTERM and SIGHUP. > >The appended diff fixes the hangs for `make -j4`->SIGQUIT by exiting >with SIGINT exit status. > >I don't consider it that ugly to report exit on SIGINT to the calling >process when the actual signal was SIGQUIT. Alternativly, we could >limit coredumpsize = 0 and then exit with SIGQUIT. I think I prefer to limit the coredump size. I thought that this bunch of changes (at least to shell and make) was ready to commit until a few minutes ago when I tried to kill a `make depend' in src/lib. It didn't work - some sub-make[s] kept running. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message