Difference between revisions of "Resources and Guidelines 2"
(Created page with '== Activity 2: Perform manual testing on the Valgrind Tool. == == Resources == * the Getting Involved page on the Eclipse Linux Tools wiki [http://wiki.eclipse.org/Linux_Tools_P...') |
(→Guidelines) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
== Guidelines == | == Guidelines == | ||
| − | *Install Valgrind on the Fedora machine | + | *READ the User Guide for Valgrind. |
| − | *Use the Valgrind to create a C/C++ example. | + | *Install Valgrind on the Fedora machine. |
| + | *Use the Valgrind to create a C/C++ example and run the Valgrind Tool within Eclipse. | ||
*Create different manual test scenarios (i.e. C/C++ projects and expected results). | *Create different manual test scenarios (i.e. C/C++ projects and expected results). | ||
** Use the C/C++ programs that you have done at Seneca. | ** Use the C/C++ programs that you have done at Seneca. | ||
Latest revision as of 08:07, 17 March 2010
Contents
Activity 2: Perform manual testing on the Valgrind Tool.
Resources
- the Getting Involved page on the Eclipse Linux Tools wiki [1]
- User Guide for Valgrind on the Eclipse Linux Tools wiki
- especially the section on Memcheck
- Andrew Overholt's presentation (videos)
- Eclipse Community Forum - Linux Tools
Guidelines
- READ the User Guide for Valgrind.
- Install Valgrind on the Fedora machine.
- Use the Valgrind to create a C/C++ example and run the Valgrind Tool within Eclipse.
- Create different manual test scenarios (i.e. C/C++ projects and expected results).
- Use the C/C++ programs that you have done at Seneca.
- Create some C/C++ programs that have memory leaks.
- Document (i.e. write) the test scenarios.
