Date: Fri, 11 Jun 2004 01:28:40 -0700 From: Sean McNeil <sean@mcneil.com> To: Daniel Eischen <eischen@vigrid.com> Cc: freebsd-threads@freebsd.org Subject: Re: signal handler priority issue Message-ID: <1086942520.10026.41.camel@server.mcneil.com> In-Reply-To: <Pine.GSO.4.10.10406110358250.12394-100000@pcnet5.pcnet.com> References: <Pine.GSO.4.10.10406110358250.12394-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> No, the problem is because SIGUSR2 is _not_ blocked. I read > "masked off" as "blocked" (the desired behavior). If the > signal handler runs, that means that the signal is not blocked. > Your goal is to prevent the signal handler (for SIGUSR2) from > running until sigsuspend() is hit. Once sigsuspend() is hit, > then SIGUSR2 becomes unblocked, the signal handler is run, > and sigsuspend() returns. This is exactly what boehm-gc is doing. There must be something else lurking in here that I've missed. I have to keep looking at it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1086942520.10026.41.camel>