rtems_message_queue_receive

[chrisj at rtems.org (Chris Johns)]

Ian Caddy wrote:
> 
> I don't think the problem is at the ISR level, but that something is 
> wrong with your tasks.  The easiest way to check this is to see if the 
> idle task is running at all.  Put a breakpoint in the idle task loop and 
> see if you get there once things go spacko.
> 
> The other option is to just break using the BDM and check where it is in 
> code.  If it is always in a particular thread, then chances are it is 
> hogging the processor and that lower priority tasks are not getting to 
> run.  If your tools contain profiling, then this will tell you where you 
> are getting stuck, but the breaking the BDM every so often is also a 
> good indicator.
> 

Another tool is the Capture Engine. If you have the RTEMS monitor 
running on a console you can enable the Capture Engine and see where the 
task flow is going. The wiki has a page on the Capture Engine under the 
Debugging Hints page or just enter 'Capture' into Find.

-- 
  Chris Johns