RTEMS stack checker
Miller, Scott A.
scott.miller at swri.org
Thu Jan 15 17:27:43 UTC 2015
The problem was with my printk_plugin. I didn't have the the correct variable arguments setup, and when I was printing, the values for the format string were memory areas not assigned to the variables. Now that I'm passing the variable arguments, the stack checker appears to be working well.
Thanks for the response, Joel.
On Jan 14, 2015, at 5:28 PM, Joel Sherrill <Joel.Sherrill at OARcorp.com<mailto:Joel.Sherrill at OARcorp.com>> wrote:
On 1/14/2015 5:18 PM, Miller, Scott A. wrote:
Attempting to get the stack checker in RTEMS enabled our software.
Before confdefs.h is included, along with all of our other CONFIGURE variables, I have put:
When I later make the call to rtems_stack_checker_report_usage_with_plugin(), I get output (one per line) for each task running (and the interrupt context), but the values printed (stack begin area, used, etc..) are all the same for each task, and the stack size doesn't seem to match the memory area allocated for the stack. The values don't seem trustable.
Is there something I'm missing to use the stack checker properly?
That doesn't seem right at all. Calling the "with plugin" variant requires you
to pass something that has a signature like fprintf(). Did you call that method
directly or via the wrapper rtems_stack_checker_report_usage()?
Can you run the fileio sample and try the stackuse command? That test should
Running RTEMS 4.10.
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill at OARcorp.com<mailto:joel.sherrill at OARcorp.com> On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users