Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!news2.arglkargh.de!nuzba.szn.dk!pnx.dk!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Markus Elfring <Markus.Elfring@web.de>
Newsgroups: comp.programming.threads,comp.unix.programmer
Subject: Re: Safe accesses of global arrays in signal handlers?
Date: Thu, 27 Sep 2012 11:20:14 +0200
Lines: 11
Message-ID: <acik2gF3panU1@mid.individual.net>
References: <accvmcFog2gU1@mid.individual.net> <pan.2012.09.25.11.15.59.228000@nowhere.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net zhJm2mtLY0t6NfYjUmatEQZ5vfuvH5b9sosLo+D4KO22M++UdGfyn03ShaLHY8Eb3S
Cancel-Lock: sha1:ZfuX0lN5kXKPCTylDRNqfUQKe1E=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120825 Thunderbird/15.0
In-Reply-To: <pan.2012.09.25.11.15.59.228000@nowhere.com>
Xref: csiph.com comp.programming.threads:1095 comp.unix.programmer:3343

> The recommended way to handle signals is to block all relevant async
> signals in all threads, then have a single thread which does nothing but
> poll signals using sigwaitinfo() then handle them (e.g. by notifying
> condition variables, appending information to a queue, etc).

Do you know any other solutions which can work without such an initial signal
blockage like it is needed in the suggested approach for the handling of
real-time systems?

Regards,
Markus