From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Weber Date: Tue, 17 Apr 2007 08:21:10 -0500 References: <200704161449.27506.jweber@domain.hid> <200704161627.01925.jweber@domain.hid> <17955.60369.329951.993803@domain.hid> In-Reply-To: <17955.60369.329951.993803@domain.hid> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704170821.10282.jweber@domain.hid> Subject: Re: [Xenomai-help] page faults List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Xenomai Help On Monday 16 April 2007 16:34, Gilles Chanteperdrix wrote: > Jeff Weber wrote: > > On Monday 16 April 2007 15:43, Gilles Chanteperdrix wrote: > > > If the fault you observe is due to an access to some memory after a > > > call to fork or one of its derivative (such as system, popen, etc...), > > > the patch would have copied the whole real-time process address space > > > at fork time instead of setting up COW mappings. > > > > No process forks are involved. Though mlockall() was called from Linux > > main(), and the page fault was encountered by a separate Xenomai task. > > Here's the task history: > > The fork may well be hidden in some library. The best way to know if > there is really no fork is to register a callback with pthread_atfork. pthread_atfork confirms that there is no fork. Jeff -- Jeff Weber American Superconductor Corp.