From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 29 Jul 2009 18:05:17 +0200 From: Philippe Gerum In-reply-to: Message-id: <1248883517.3532.7.camel@domain.hid> MIME-version: 1.0 Content-type: text/plain Content-transfer-encoding: 7bit References: <1248453047.3998.168.camel@domain.hid> <1248461458.3998.183.camel@domain.hid> <1248517986.4438.1.camel@domain.hid> <1248855797.3247.16.camel@domain.hid> Subject: Re: [Xenomai-help] Stack sizes etc. (Re: POSIX skin/Blackfin: SIGSEGV when stracing or gdb'ing) List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenoka09@domain.hid Cc: xenomai@xenomai.org On Wed, 2009-07-29 at 13:40 +0200, Kolja Waschk wrote: > Hi, > > > One of the problems appears when the following code is run via > > gdbserver, a breakpoint is hit at main() and I "step" over > > rt_task_shadow: > > > >> Xenomai: fatal: xnshadow_relax() failed for thread maintask[222] This may be an I-pipe issue. As I understand, you are currently running 2009R1-RC2 unmodified, could you summarize where the various Xenomai related components come from so I could try looking at the issue? e.g. I-pipe/Adeos patch from uclinux-dist's bfin_patch/adeos_patches/ ? Xenomai 2.4.7 support from xenomai.org? There are two different sources for the I-pipe support for Blackfin, so it is important to know which one comes into play here. > > I just observed the same without gdb in play, with main extended a bit, > creating a second (RT) thread from main (after rt_task_shadow in main). > > Xenomai: fatal: xnshadow_relax() failed for thread logger[219] > CPU PID PRI TIMEOUT STAT NAME > 0 0 50 0 00400088 ROOT > 0 217 50 0 00300380 maintask > > 0 219 50 0 00300380 logger > Master time base: clock=74044591006 > > However, it doesn't happen with the simple example I posted last week. > Maybe I can find some evolutional stage between that example and my > larger application that just causes the failure. > > Kolja -- Philippe.