Remember to install them via the apt-get command in the Dockerfile. It’s indeed way more elegant than a VM, but still very inflexible: what if my program has dependencies? Well, I need to

Of course, I’m not the first person to come up with this solution. Yeah yeah, I know, it’s kind of a trend to use Docker everywhere, but here it really makes sense. Solutions seem very very bulky and inefficient I just want to be able to run Valgrind on a project in a way that canĮasily be automated (for CI purposes for example, or even local tests). A VM is another solution, but all of these “heavy” I don’t have the necessary realĮstate for that on the MacBook, so that’s out of the question. I mean, there are relatively simple solutions to this. The latest version of Valgrind does not support macOS > 10.13. (macOS High Sierra) is not supported (I run macOS 10.14 which is definitely not the latest version right now): The problem is that I often develop on my MacBook, and as of the time of this writing, any macOS release past 10.13 It actually does much more than simple memory leakĬhecks it can even help spot times where you use uninitialized variables for example, even if the bug doesn’t come up Valgrind throughout (and even before) my uni years, and I love it. Helping you verify that your program does not have memory leaks: Valgrind. The trouble is that you often forget to free some of it, or accidentally free stuff twice. That means that you usually need to go and “ask”įor a piece of memory via malloc() or something like that, and then you’re supposed to free it using, well, free(). Leak? Well, in C and C++ (but mostly C), you manage memory manually. If you have developed anything on C/C++, you probably have gotten into dreaded memory leak problems.

Valgrind for mac os sierra