Hi, Mario.

I recently fixed that in the docs. Here's what they say now:

Send a signal to a specific thread, depending on the situation:

    * If used with MsgSend*(), MsgReceive*(), and MsgDeliverEvent(), the
thread is the one identified by the rcvid that MsgReceive*() returns.
    * For timers, it's the thread that called timer_settime().
    * For InterruptAttach() and InterruptAttachEvent(), it's the thread
attaching to the interrupt.
    * For asyncmsg_channel_create(), it's a random thread in the process.
    * For SyncMutexEvent(), it's the thread that called the function.

In the case of timers, SyncMutexEvent(), and interrupts, if the thread dies
before the event gets delivered, the kernel sends the signal to a random
thread in the same process. 


Steve Reid (stever@qnx.com)
Technical Editor
QNX Software Systems 
 

> -----Original Message-----
> From: Mario Charest [mailto:mcharest@zinformatic.com] 
> Sent: Tuesday, April 01, 2008 12:57 AM
> To: ostech-core_os
> Subject: Doc on SIGEV_SIGNAL_THREAD
> 
> The doc on SIGEV_SIGNAL_THREAD says: "Send a signal to a 
> specific thread".  To me specific mean to a thread of my 
> choosing.  That doesn't seems to be the case since the macro 
> doesn't provide an argument for TID.  Hence I must conclude 
> that it will send the signal to the thread that created the 
> event or maybe registered it.
> 
> That all seems vague to me?
> 
> - Mario
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post6316
>