In an ideal world, all errors are carefully logged, and it only takes a couple of commands to locate a place to start troubleshooting. But realistically, there will be instances wherein the errors or issues are less obvious. In these instances, we can use `ltrace` and `strace` to trace library and system calls, respectively to aid in locating the issue. In this hands-on lab, we’ll do just that to discover the cause of an issue with an application.
_This course is not approved or sponsored by Red Hat._
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Attempt to Run Executable
Attempt to run the executable at
/opt/servercheck.- Check for Memory Leaks
Use
valgrindto determine if the application has any memory leaks.- Track Error
Track library and system calls to discover the issue.
