Wolfgang Grandegger wrote:
> Gilles Chanteperdrix wrote:
> > On Dec 10, 2007 4:20 PM, Wolfgang Grandegger <[EMAIL PROTECTED]> wrote:
> >> Gilles Chanteperdrix wrote:
> >>> Wolfgang Grandegger wrote:
> >> # ./kill_pthread
> >> Starting high_prio_task
> >> low_prio_task: policy=1 prio=10
> >> Killed low_prio task: count=172709970, overruns=0
> >> + Stopped ./kill_pthread
> > What you are observing is probably a difference between linuxthreads
> > and NPTL: with linuxthreads, SIGSTOP can be sent to a particular
> > thread and will cause this thread only to stop. With NPTL, it seems
> > that the effect of SIGSTOP is global, it affects the entire process. I
> > will test tonight on my x86 box to see if I observe the same effect.
> Ah, the man page says:
> Note that pthread_kill() only causes the signal to be handled in the
> context of the given thread; the signal action (termination or stop-
> ping) affects the process as a whole.
I can confirm the same effect on plain Linux. So, the newly added
pthread_kill is not to blame (yet).
Xenomai-core mailing list