In this hands-on lab, you will be evaluating an application for memory related issues. You have two applications with possible memory leak or other memory errors. In order to evaluate the applications, you will use the `valgrind –tool=memcheck` utiity to monitor the memory usage for each application. For the final task, you will launch a different application and use the `valgrind –tool=cachegrind` command to determine if the application in question has memory caching issues.
*This course is not approved or sponsored by Red Hat.*
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Evaluate the evolk Application
- Use the
valgrind memcheck. - Include the following parameter information. You can refer to the
Valgrindhelp or man pages for details.- Which tool to execute.
- If the command should check for memory leaks.
- Should reachable memory issues be included.
- Set the number of callers to 20.
- Track open file descriptors.
- Write the results to stdout.
- Review the command output to determine if there are any memory leaks or errors.
- Use the
- Evaluate the evoerr Application
- Use the
valgrind memcheckutility. - Include the following information. You can refer to the
Valgrindhelp or man pages for details.- Which tool to execute.
- If the command should check for memory leaks.
- Should reachable memory issues be included.
- Set the number of callers to 20.
- Track open file descriptors.
- Write the results to a log file.
- Review the log file and determine if any the application has any errors listed.
- Use the
- Evaluate the evoche Application
- Use the
valgrind cachegrindutility. - Include the following information. You can refer to the
Valgrindhelp or man pages for details.- Which tool to execute.
- Write the results to a log file.
- Review the log file using cat, less or more, or a text editor checking for any
misses. - Use the
cg_annotatecommand to review the cachegrind.out* file and determine if any the application has any errors listed.
- Use the
