From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <446DDA56.3050209@domain.hid> Date: Fri, 19 May 2006 16:46:46 +0200 From: Philippe Gerum MIME-Version: 1.0 Subject: Re: [Xenomai-help] rt_task_delete behavior References: <6ee4c8380605172215i34e83797i709de4a314412618@domain.hid> <446C29A9.3030508@domain.hid> <6ee4c8380605190702l323f5d57v234d055b1cfeff5a@domain.hid> In-Reply-To: <6ee4c8380605190702l323f5d57v234d055b1cfeff5a@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Brian L." Cc: xenomai@xenomai.org Brian L. wrote: > CPU PID PRI TIMEOUT STAT NAME > 0 0 0 0 R ROOT > Is this snapshot obtained while the application is still hanging? > > On 5/18/06, Philippe Gerum wrote: > >> Brian L. wrote: >> > I'm calling what amounts to rt_task_delete(rt_task_self()) and the >> > task simply hangs, with this call never returning. >> > rt_task_delete(NULL) behaves identically. >> > >> > What could cause this behavior? The problem is embedded within a >> > nontrivial application, but it seems that it's not behaving according >> > to spec which says that the caller will only block when: >> > >> > 1. The target is in a "safe section" >> > >> > and >> > >> > 2. The caller is not the target >> > >> > Any ideas? >> > >> >> Could you post the output of >> >> $ cat /proc/xenomai/sched >> >> TIA, >> >> > _______________________________________________ >> > Xenomai-help mailing list >> > Xenomai-help@domain.hid >> > https://mail.gna.org/listinfo/xenomai-help >> > >> >> >> -- >> >> Philippe. >> > -- Philippe.