Sooooo I learn c. Programmed antivirus project last night, and there is 13, 374 bytes of memory leak. (BTW the program crashes at return 0). *Rage and despair*

How about if you compile it without stripping debugging symbols? Wasn't valgrind able to show you the lines where the leaks happened?

And how about compiling it with address sanitization? That could point to some pointer magic losses.

@Aldar I am using drmemory... Should I use something else?

@EladMatia I can only recommend Valgrind, used it at school, it has a pretty similar output to this, and can only recommend it.
Or find out if your mem debugger supports linking it further, to show you at least which function leaked.

Bug will get inside if you leave windows open, not Linux...😎