Integrate Valgrind Memory Check Tool to LTP
Get series with b4
b4 am 20090824093204.31997.18175.sendpatchset@subratamodak.linux.ibm.comVersions newest first
- v1 Latest2 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Create the necessary Interface with runltprunltp | +35 | 0 replies | |
| 2/2 | Script that will actually create the COMMAND File entriestools/ | +106 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [LTP] [PATCH 00/02] Integrate Valgrind Memory Check Tool to LTP
Hi,
Introducing and Integrating the Valgrind Memory Leak Check tools to LTP. This again is in line with the OLS 2009 paper where we proposed that memory leak check for LTP test cases will become part of LTP soon.
Valgrind is one of the best Memory Leak Check tools available to the open source community and being widely used by many maintainers of Open Source Projects to regularly check the health of their code. On similar lines, we would like it to check the various dynamic issues related to Memory Leaks, Thread Concurrencies for the LTP tests so that we minimize those errors for the LTP tests. The following set of Patches will:
1) Integrate within LTP infrastructure the use of VALGRIND tool,
2) Internal check against unavailability of this tools on your machine,
3) Running through runltp, the various:
3.1) Memory Leak Checks,
3.2) Thread Concurrency Checks,
on all LTP tests that the user intents to run/check,
4) Comparisn of how a normal test run differs from the the test run through Valgrind,
Now, you may ask the question why don��t we use Valgrind independantly ? True, it can be done. But, it becomes more simple when we can ask runltp to do the job for us and remaining everything remains in LTP format. And, this is handy for test case developers who can do a quick check on the tests they have just developed.
When you want to run your tests/sub-tests through Valgrind tool, what you have to just do is:
./runltp -f <your-command-file> -M [1,2,3]
CHECK_TYPE=1 => Full Memory Leak Check tracing children as well CHECK_TYPE=2 => Thread Concurrency Check tracing children as well CHECK_TYPE=3 => Full Memory Leak & Thread Concurrency Check tracing children as well
The above options in LTP will usher in better Test Case development.
Regards--
Subrata
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list