From owner-freebsd-hackers Tue Feb 3 16:37:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06147 for hackers-outgoing; Tue, 3 Feb 1998 16:37:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from jraynard.demon.co.uk (jraynard.demon.co.uk [158.152.42.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06049 for ; Tue, 3 Feb 1998 16:37:09 -0800 (PST) (envelope-from fhackers@jraynard.demon.co.uk) Received: (from fhackers@localhost) by jraynard.demon.co.uk (8.8.8/8.6.12) id AAA11848; Wed, 4 Feb 1998 00:36:26 GMT Message-ID: <19980204003626.08784@demon.co.uk> Date: Wed, 4 Feb 1998 00:36:26 +0000 From: James Raynard To: freebsd-hackers@FreeBSD.ORG Subject: sigprocmask.S - help requested! Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" I'm trying to tackle the NSIG=32 barrier by changing sigset_t from an int to an array. Having uncovered a rather disappoining amount of code that assumes sigset_t == int, I've reached a stage where I can compile a new kernel, reboot, login and run "normal" code; however, I've noticed that anything involving blocking signals fails because sigprocmask(SIG_UNBLOCK,...) doesn't restore the old signal mask. It seems that the sigprocmask call gate is rather "different", and I don't know enough about GAS or call gates to understand what's going on. Can anyone help me out? (Diffs to follow when I'm happy with them).