This lab will give you experience using both Valgrind’s code checking tools. Clone the repo down and proceed as usual.
You will need to create a file named
answers.md to write responses
You know the drill.
.gitignore file and add stuff you want to ignore.
You will lose points…
Problem1directory and take a look at the project. It’s a linked list similar to the problem from last time.
Problem2directory and take a look at the source files in the project.
Build and run the code through Valgrind. Were you right? If not, how did things differ?
Why do you think there is a difference between the
Note that you don’t need to fix any code for Problem 2.
Problem3directory and take a look at the source.
You will be graded on:
.gitignoreand absence of junk files.
As always, your git repo on http://git-classes.mst.edu is your submission. Don’t forget to commit and push all relevant files. Make sure you see everything you expect on GitLab!
We expect to see the following files on your master branch:
Notice that your repository has subdirectories! You have the
option to put one
.gitignore file at the root of your repo, or
.gitignore files in each subdirectory if you prefer.
The Leak Summary has 5 sections: “definitely lost”, “indirectly lost”, “possibly lost”, “still reachable”, and “suppressed”. ↩