|
From: Nuno L. <nun...@sa...> - 2008-06-22 22:12:26
|
> So I have a background build system that ticks away building stuff, > running unit tests under valgrind... > > Now I have just added the facility to run unit tests with gcc mudflap > on as well. > > Question: What is the interaction (if any) between mudflap and valgrind? none special.. > Is their any benefit in running the mudflap and valgrind > simultaneously? Or is it better just to do two separate builds & runs? I would run it separately, as mudflap will trigger some valgrind/memcheck warnings (you can always suppress them, but..). Anyway it may be even faster to run the unit tests twice. > Or will valgrind detect all flaws that mudflap detects in any case? > (My understanding is, (correct me if I'm wrong), mudflap has a finer > grained/more precise understanding of array sizes, bounds, and > indexing than valgrind.) Valgrind does not detect everything that mudflap detects and vice-versa. Mudflap detect some stack-related things that valgrind won't report. Nuno |