On Wed, Sep 17, 2014 at 10:45 PM, Mohammed Saeed Khoory <mohammed.kho...@eiast.ae> wrote: > I'm not sure about tools similar to valgrind, but you might find it useful to > enable deep memory tests in RTEMS. You can find more information here. > http://www.rtems.org/wiki/index.php/Debugging#Optional_Compile-time_Selections >
Thanks Mohammed, we're already using the heavy stack check; I'll see what can be done in terms of concurrency checking (specially race conditions). I'll check Chris' mail. Daniel. > By enabling these macros you can check if your memory is getting corrupted > everytime a system call occurs. This is very useful in debugging and has > saved me a lot of headaches personally. You can detect stack and heap > corruption with these macros. > > I don't think it would detect memory leaks however. > > Hope this helps > >> -----Original Message----- >> From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Daniel Gutson >> Sent: Thursday, September 18, 2014 3:02 AM >> To: RTEMS >> Subject: dynamic checking tools >> >> Hi guys, >> >> 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. >> >> Thanks! >> >> Daniel. >> >> -- >> >> Daniel F. Gutson >> Chief Engineering Officer, SPD >> >> >> San Lorenzo 47, 3rd Floor, Office 5 >> >> Córdoba, Argentina >> >> >> Phone: +54 351 4217888 / +54 351 4218211 >> >> Skype: dgutson >> _______________________________________________ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel -- Daniel F. Gutson Chief Engineering Officer, SPD San Lorenzo 47, 3rd Floor, Office 5 Córdoba, Argentina Phone: +54 351 4217888 / +54 351 4218211 Skype: dgutson _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
