Bruno <firstname.lastname@example.org> wrote:
Marcin Dzieciol wrote:
Brian Stecher <> email@example.com> > wrote:
Bruno <> firstname.lastname@example.org> > wrote:
There is an error in the file sys/siginfo.h :
#define SIGEV_THREAD_INIT(__e, __f, __v, __a) (
(__e)->sigev_notify = SIGEV_INTR, <----------- SIGEV_THREAD
All part of our cunning plan to get people not to use that event type > > .
why don’t use this event type ?
Creating a thread is a relatively heavyweight operation. Doing it in
response to a sigevent (which typically wants fast response) is generally
a bad idea - there is almost always a better way of writing the code.
E.g. Create a channel and use the dispatch_* functions to have a pool
of threads that block on it waiting for a SIGEV_PULSE event. If you’re
a resource manager (as all true thinking Neutrino programs should be ,
you already have the pool of threads sitting around.
Brian Stecher (email@example.com) QNX Software Systems, Ltd.
phone: +1 (613) 591-0931 (voice) 175 Terence Matthews Cr.
+1 (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8