From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4D1FA467.2030607@domain.hid> Date: Sat, 01 Jan 2011 23:02:15 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4D110810.1090504@domain.hid> <4D1A135E.7060005@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: >>> posix-cond-torture test case to verify that what was supposed to be > > As a side note, cond-torture-native (not -posix) locks up with gdbserver/gdb after > displaying just "simple_condwait". My problems seem to be not just related to the POSIX skin. Ok. I can confirm I am unable to reproduce this issue on the NPTL based setups I have access to, the LD_ASSUME_KERNEL environment variable no longer seems to do the trick to force linuxthreads. So, I could not test a linuxthreads based system. Your issue seems to be that the condvar waiting syscall is restarted whereas it should not, and indeed, native and posix condition variables work the same way. To move forward, we should follow the syscall path and see at what point it is restarted whereas it should not when running under gdb. -- Gilles.