Author: Unknown
Subject: Running Valgrind on Tests 201-203
Date: Thursday, 26 Mar 2020, 19:49:37

I wanted to make sure that I was having no memory leaks on my Deque.c implementation, so I ran valgrind (i.e. valgrind --leak-check=full /c/cs223/Hwk4/test.Qsort 201) and got lots of leaks (>2 million bytes not allocated/freed properly) and the error messages say it is due to a calloc/Perl call (even though I use neither). Is this the correct way to check any errors with memory allocation on our Deque.c implementation or should we be testing it in some other way?