From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 21 Jan 2011 15:16:08 +0100 (CET) From: Kolja Waschk In-Reply-To: <1295618431.1828.52.camel@domain.hid> Message-ID: References: <4D384CC9.2040303@domain.hid> <4D386922.5080807@domain.hid> <4D38809E.3080906@domain.hid> <4D388975.80606@domain.hid> <1295618431.1828.52.camel@domain.hid> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Sender: "Kolja Waschk,,," Subject: Re: [Xenomai-help] debug posix skin - pthread_cond_wait return EPERM Reply-To: xenoka09@domain.hid List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum Cc: xenomai@xenomai.org Hi, > primary mode loop. In that case, the gdb stub which is part of the > regular kernel just can't receive the remote "break" command packet sent > from your host, simply because the remote linux kernel is not given any > CPU time. Thanks for the clarification. I suspected so but the FAQ entry gave me some hope that I might have been wrong ;) Are there any gdb macros that might help to gather helpful information about tasks etc. with a debugger on a host attached to the target via JTAG? Kolja