From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4C700E8A.8010305@domain.hid> Date: Sat, 21 Aug 2010 19:36:10 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <1282047938.5255.89.camel@domain.hid> <4C6B146D.9010004@domain.hid> <1282126974.5255.262.camel@domain.hid> <4C6BBD62.3050907@domain.hid> <1282131617.5255.286.camel@domain.hid> <4C6BCB51.4010805@domain.hid> <1282133876.5255.296.camel@domain.hid> <4C6BD403.4030902@domain.hid> <1282136147.5255.306.camel@domain.hid> <4C6BE297.4060706@domain.hid> <1282140262.5255.313.camel@domain.hid> <4C6BE9D3.1080907@domain.hid> <1282141537.5255.315.camel@domain.hid> <4C6BEE9B.1080000@domain.hid> <1282144162.5255.325.camel@domain.hid> <4C6BF8B1.8080206@domain.hid> <1282297638.5255.373.camel@domain.hid> <4C6E50C1.9040700@domain.hid> <1282319427.5255.400.camel@domain.hid> <4C70079D.4010502@domain.hid> In-Reply-To: <4C70079D.4010502@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] xenomai 2.5.3/native, kernel 2.6.31.8 and fork() List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai@xenomai.org Gilles Chanteperdrix wrote: > There are other issues to consider, such as detecting that a private > mutex created in the father continues to be used in the child. A simple fix for this would be to keep a list of mutexes in the native and posix skin, and nullify their magic/opaque pointer at fork. The problem is that there is no more room in pthread_mutex_t, so we will have to malloc at pthread_mutex_init time. -- Gilles.