Profiling Viewer for macOS opens and visualizes callgrind files. Runs natively on both Apple silicon and Intel® based Mac computers. You can use treemap, callgraph, sortable list or call tree to identify and analyze functions where your application spends more time than expected.

Apr 28, 2018 Valgrind is a programming tool for memory debugging, memory leak detection and profiling. Its installation for macOS High Sierra seems problematic and I wanted to write this post to tell the solution that worked for me. I use Homebrew to install it which is the recommended way and the solution also uses it.

For example, you can open callgrind profiler files generated by the Xdebug extension for PHP, php-memprof, Valgrind, Ruby ruby-prof, Python cProfile with pyprof2calltree, gperftools-pprof, Golang with pprof, Node.js with Valgrind or nodegrind and many other profiling tools with callgrind file output.

1. Valgrind mojave. How to install Valgrind on macOS Mojave(10.14) with Homebrew, A (rather painful) install from source workaround based on this patch, this post and this answer. $ git clone I tried to install with the command brew intall -HEAD Valgrind instead, after successfully installed the dependencies autoconf, automake and libtool, when.
2. Valgrind on Mojave using Docker 2019-11-29 Valgrind is a very useful tool that allows you to spot memory leaks, memory corruptions and other bugs in your program which would have otherwise been difficult to find and track down.

Xdebug 2.6 (and later) added support for memory profiling php scripts. Profiling Viewer already handles multiple types of costs. Just open the generated file and select between Time and Memory costs types.

Treemap

Function costs visualized as Treemap. The color schema of the treemap is selectable between palette or heatmap. In heatmap mode you can combine the main metrics with a secondary metrics. The main metrics (eg. Time) determines the size, the secondary metrics eg. callcount or any other available costs determines the color of an area on the heatmap.

Callgraph

Function costs visualized as Callgraph. You can combine up to three metrics to build the callgraph. The main metrics (eg. Time) determines which functions will be displayed on the callgraph and is represented by the thickness of the connections between the nodes. You can use callcount or any other available cost to control the color (heatmap) and the area (size) of the call graph nodes. The callgraph complexity can reduced by hiding functions with cost below a customizable preset. The node shape is also customizable.

The callgraph is zoomable and understands trackpad gestures like zoom in, zoom out, smart zoom. You can drill down through double-click, mouseover for details

Sourcefile viewer

The loaded source code is annotated with costs. You can define where your source codes located and when required, how these locations should be mapped to the server path found in callgrind file. Profiling Viewer opens the source code of the selected function and annotates its lines with the corresponding costs.

Reports: Print or PDF

Print or export reports as PDF with Treemap and Callgraph

Suppress functions

Functions can be suppressed based on the source file path. For example, you can use this feature to hide system functions to get a better overview of your own code. For some languages a customizable preset is included. You can extend this preset with your own paths.

Other features

• Displays function calls as call tree
• Handles multiple types of costs and positions
• Parses compressed callgrind files
• Displays costs as raw data, as selected unit or as percent
• Navigation history
• Supports Dark Mode
• Runs natively on both Apple silicon and Intel® based Mac computers
• Works with 11 (Big Sur), 10.15 (Catalina), 10.14 (Mojave), 10.13 (High Sierra), 10.12 (Sierra), 10.11 (El Capitan), 10.10 (Yosemite), macOS 10.9 (Mavericks)
• Small memory footprint (for example, approximately 280 MB memory used to open and display a 4.6 GB callgrind file generated by xdebug)
• Opens callgrind files generated by Valgrind, Ruby ruby-prof, the Xdebug extension for PHP, php-memprof, Python cProfile with pyprof2calltree, gpertools pprof, go programs with pprof, Node.js with nodegrind and most other callgrind files
• You can open callgrind files via Command Line too

Question or issue on macOS:

I tried to install Valgrind with brew install Valgrind and got :

I tried brew install –HEAD Valgrind.

Instead, after successfully installing the dependencies autoconf, automake and libtool, when it tries to install valgrind, I get a configure error:

My OS is macOS Mojave(10.14), so does it mean that I can’t install a functioning Valgrind with Homebrew presently?

How to solve this problem?

Solution no. 1:

A (rather painful) install from source workaround based on this patch, this post and this answer.

If you get the following error: No rule to make target '/usr/include/mach/mach_vm.defs’, you will need to run xcode-select --install. You might need to install Xcode from the app store if you don’t already have it. Once that’s done, you will need to edit the coregrind/Makefile:

Search for:

After double checking the below folder exists, prefix every line with:

End result should be:

Now run make again and the includes should be found. But that doesn’t necessarily mean it will compile. I got the following error:

A fix for this is to add the following line:

to the following files:

Compile And Install Valgrind On MacOS Mojave (10.14.2) – 箱猫日和

• coregrind/m_syscall.c
• coregrind/m_syswrap/syswrap-darwin.c
• coregrind/vg_preloaded.c

Finally, you need to cross your fingers hoping no other errors show up:

Solution no. 2:

You may use Experimental Version of Valgrind for macOS 10.14.5 Mojave at:

The command to use it is:

It is still experimental and needs some work but for simple projects works already… Enjoy!

Solution no. 3:

addition: I found this one worked for me on my OSX 10.14

A branch that is working to get OSX correct. something to tide us over until we get a real valgrind version fixed.

Solution no. 4:

I am having the same issue. It seems like valgrind is not compatible with the newest macOS(10.14 Mojave). Tried installing it the High Sierra way (https://www.gungorbudak.com/blog/2018/04/28/how-to-install-valgrind-on-macos-high-sierra/) and got the same output you described. The only solution I can offer you right now is either working on virtual machine (https://www.virtualbox.org/) or using Docker (https://www.gungorbudak.com/blog/2018/06/13/memory-leak-testing-with-valgrind-on-macos-using-docker-containers/).

Solution no. 5:

I have just found a working solution to use VALGRIND on my Mac (Mojave 10.14.6). Just run this command :

(From https://github.com/LouisBrunner/valgrind-macos)

Hope it will work for you.

Solution no. 6:

Not a proper solution for macOs, but for the time being, I created a docker image. After installing docker for macOS, this is how to start valgrind:

Solution no. 7:

As of 2019-NOV-30, it is possible to build against OS X 10.14.6 via https://github.com/sowson/valgrind and https://github.com/LouisBrunner/valgrind-macos

However, there are many test failures (see the LouisBrunner link), noise during runs, and SEGVs when running against non-trivial programs: installing is, well, installing. YMMV.

Solution no. 8:

You can follow alex.m’s answer to get valgrind, but if you’r using it on a int main() { return 0; } program, you’ll get many weird errors, and non-existing allocs / free.

To ‘hide’ these annoying errors, you can follow theses steps (it’s more a workaround than a real fix) (based on this wiki page and some research in Valgrind’s source code):

See All Results For This Question

• First, create and compile a int main() { return 0; } program.
• Execute the following command (to create file containing error suppression):

valgrind --leak-check=full --show-reachable=yes --error-limit=no --gen-supressions=all --log-file=$YOUR_LOG$ $YOUR_BINARY$

• Using this gawk script, create the .supp valgrind file:

cat ./$YOUR_LOG$ | ./$YOUR_SCRIPT_FILE$ > minimal.supp

• Copy and Past minimal.supp content at the end of $YOUR_VALGRIND_INSTALLATION_PATH$/lib/valgrind/default.supp file

And you are done! Weird and nonexistent errors will be ignored.
If you also want’s to remove the non-existing allocs, frees etc, you can directly edit Valgrind’s source code. Or just use heapusage for leak-tracking

Solution no. 9:

(works on mojave 10.14.6)

Solution no. 10:

As others have mentioned, Louis Brunner maintains a working version at https://github.com/LouisBrunner/valgrind-macos.

This worked for me for MacOS 10.15.7 Catalina.

See Full List On Github.com

Hope this helps!