On Thu, 2006-11-23 at 15:25 +0000, Daniel Schnell wrote: > Hi, > > our application deadlocks from time to time. > > To isolate which of the threads are deadlocked, I look > into /proc/xenomai/stat. Here I can see if there are context switches > happening or not. Further I can see which threads have which PID and > which task state they are into. One of the task states that is not > clear to me btw is the state "X" or "relaxed shadow". Anybody ? >
It's running under the control of the Linux scheduler (secondary mode). The fact that SIGINT seems blocked for your application over GDB is no good sign, and this is what needs to be investigated. Is SIGINT properly handled (i.e. causing GDB to take control back) before your application enters this wild state? E.g. does hitting ^C over GDB while your application is initializing, and maybe later during the routine processing work? When does this apparently stop working? I'm trying to find out whether the fact that SIGINT is not being caught anymore is related to the deadlocked state here. Another thing: what does 'ps' say when the application looks deadlocked? -- Philippe. _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
