From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <52558563.2010408@xenomai.org> Date: Wed, 09 Oct 2013 18:33:39 +0200 From: Philippe Gerum MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] t_suspend and XNBREAK List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Daniel Merrill , xenomai@xenomai.org On 10/09/2013 06:29 PM, Daniel Merrill wrote: > All, > > > > I'm hoping maybe someone can shed a little more light on the issue we see > occasionally. Occasionally our code using the psos+ skin will fail a > t_suspend(0) with error code -4, which I found to be EINTR and appears to > be set if the XNBREAK flag is set. After digging around in the > documentation I found some references that seem to indicate that this > means the thread was forcibly unblocked for some reason. Is there some way > to diagnose what caused this (I'm having trouble pinpointing anything)? It > appears when debugging that the thread never really suspends at all but > returns immediately from the call. Does anyone have some pointers on what > might be a good place to start looking for the culprit? Thanks in advance. Are you tracing the application with GDB? > > > > > > Dan Merrill > > _______________________________________________ > Xenomai mailing list > Xenomai@xenomai.org > http://www.xenomai.org/mailman/listinfo/xenomai > -- Philippe.