Considering that posix signals are not real-time *anyway*, using them
to programme specific treatments per-thread is hmmm... say a nightmare
! Plus I don't quite see how you could eventually have a non-broken
implementation. Gerd Stolpmann emphasized it if I understood well.
One solution would be
Am Montag, den 26.10.2009, 12:06 -0700 schrieb yoann padioleau:
> On Mon, Oct 26, 2009 at 11:36 AM, Till Varoquaux wrote:
> > You'd have the same problem in any other programming language; this is
> > due to the underlying POSIX model.
> > The POSIX standard mentions that alarms are global to the
On Mon, Oct 26, 2009 at 11:36 AM, Till Varoquaux wrote:
> You'd have the same problem in any other programming language; this is
> due to the underlying POSIX model.
> The POSIX standard mentions that alarms are global to the process [1].
>
> " There were two possible choices for alarm generation
You'd have the same problem in any other programming language; this is
due to the underlying POSIX model.
The POSIX standard mentions that alarms are global to the process [1].
" There were two possible choices for alarm generation in
multi-threaded applications: generation for the calling thread
Hi,
I would like to create different threads where each thread do some
computation and are subject to different
timeout. Without threads I usually use Unix.alarm with a SIGALARM
handler that just raise a Timeout exception
and everything works fine, but when I try to do something similar with
threa
