From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4C095876.3060605@domain.hid> Date: Fri, 04 Jun 2010 21:48:06 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : native: Rework handling of pthread carrier thread List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai-core GIT version control wrote: > Module: xenomai-jki > Branch: for-upstream > Commit: 0352b068600bd4ef3172c8a42416badbcdad32ca > URL: http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=0352b068600bd4ef3172c8a42416badbcdad32ca > > Author: Jan Kiszka > Date: Wed Apr 28 15:08:11 2010 +0200 > > native: Rework handling of pthread carrier thread > > This patch improves two pitfalls of libnative's interaction with > underlying pthreads: > > First, it tries to detect double deletions (cancellations or joinings) > of pthreads and report them via an error code. This reduces the risk to > trigger a SIGSEGV accessing meanwhile released pthread objects. And > second, it properly detaches joinable pthreads when they are deleted > instead. This properly releases the pthread resources. I really do not understand that. What is the point of creating a joinable thread if you do not want to join it once it has been canceled? -- Gilles.