ThrowTheSwitch
New plugin proposal: Memory Testing
One thing that I've done outside of Ceedling, but I would like to see done in Ceedling is running a memory analyzer like Valgrind or Dr Memory as an option. Out of curiosity how many people would like a plugin like this in Ceedling?
One open question I have if people want this is: How do we want this implemented? Do we just want to run Valrind or Dr Memory on the executable after we've collected the test results or would we want this to be like the gcov plugin that builds a separate executable for each test in an isolated environment?
I am interested in having this option. I'm actually ran across this issue whilst googling trying to find how to integrate valgrind...
An a previous project we used a shell script that just ran valgrind on the test executables without really doing anything special re: environment and it seemed to work just fine. I don't really have a strong preference either way though.
Just my $0.02
@mvandervoord I have a few questions on the implementation. In my mind, you would choose to do a memory test separate from actually running a test. Since all that needs to happen is the objects need to be run with a different executable, I'd figure that the plugin not worry about its own objects in contrast right now with the gcov plugin builds which everything separately.
However, I'm curios about about two things:
-
Is it viable to check if objects are generated or need to be updated before a plugin runs. I.E. If I want to run a memory test on test_foo.c and I run the command
ceedling memcheck:foo, is there a way to verify that test_foo.out has already been generated and is updated? -
Along the same lines, is there a way to suppress tests results if someone just wants to run the memory check?
Just wanted to hear if anyone have done any work towards getting the unittests to run under Valgrind? Anything to share?
I've created a merge request that attempts to fix the command_hook plugin. https://github.com/ThrowTheSwitch/Ceedling/pull/307
After linking I'm able to use Valgrind with the hook. Agreed, best scenario would be to create a Valgrind plugin - the above merge makes the command_hook work how I thought it was supposed to work.
This feature seems to be implemented by now, maybe this issue could be closed? https://blog.zaleos.net/unit-testing-c-code-with-ceedling-and-cmock/
It seems that we can use Valgrind via command_hooks. The article linked by @ojousima also uses the command_hooks approach.
That said, we can also add a Valgrind plugin to provide a more seamless integration of Valgrind with Ceedling. I can work on this and raise a PR to eventually close this issue.
