From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4D1A135E.7060005@domain.hid> Date: Tue, 28 Dec 2010 17:42:06 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4D110810.1090504@domain.hid> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] gdb/gdbserver and pthread_cond_wait List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kolja Waschk Cc: Xenomai GNA Kolja Waschk wrote: > Hi, > > I've made up a small test program for my issue with pthread_cond_wait and gdb. > Sorry for posting code again, I've made it as compact as possible. It would have been nice if you had posted the code in the mail body, instead of attaching it, this would have allowed us to comment it. So, here is the comment without the code. When pthread_cond_wait fails, if you enter pthread_cond_wait again, it will fail again, forever, and you get a lockup. sched_yield will likely not change anything. What you should do is remove the printf when there is no error. And when there is an error, print the error, then exit. Now, about pthread_cond_wait, the error looks a lot like something which was supposed to be fixed in the 2.5 branch. Could you run the posix-cond-torture test case to verify that what was supposed to be fixed is indeed fixed with the libc/gdb combination you are using? -- Gilles.