dynamic checking tools

[Joel Sherrill]

On 9/17/2014 6:23 PM, Chris Johns wrote:
> On 18/09/2014 4:01 am, Daniel Gutson wrote:
>>     are there any dynamic checking tools (a la
>> valgrind/helgrind/memcheck/drd and *sanitizer) for RTEMS?
>> More specifically, I'm interested in memory and concurrency checking,
>> more specifically for ARM.
>>
> None that I know of. My limited understanding of these tools is their 
> use of MMU features to work and the resultant effect on performance make 
> it difficult to match up with RTEMS's runtime environment. RTEMS being a 
> single process, single address space makes this sort of thing more 
> complex and that is not taking into account the real-time issues due to 
> the added overhead.
>
> In some RTEMS applications I have worked at the application level to 
> allow the code or parts of the code to run on hosts that support the 
> tools you list and then I run the code on that host. It requires 
> planning and investment of time to make this happen but the pay off is 
> well worth it. You only have to find a few issues to cover the costs. It 
> is also nice to be able to run the code and see if any issues exist when 
> chasing a problem on a target.
That was my basic premise with the Scheduler Simulator. You can
get near 100% coverage of scheduling algorithms and the supporting
code with test scenario scripts that are rarely over 15 lines long.
You can use the native gdb and gcov support easily and probably
other tools I never tried.
> Chris
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985