On Fri, Jun 26, 2020 at 3:01 PM Anuj Verma <[email protected]> wrote: > > > have you tried to use valgrind's callgrind tool + kcachegrind ? It can > > be very helpful > > No, I haven't. The problem is that I use windows for development and > valgrind doesn't work on windows.So, switching back and forth makes > the process a bit tedious. I'll try to use it on WSL2.
you also have DrMemory on Windows memory errors and leaks, and the Visual Studio tools (https://docs.microsoft.com/en-us/visualstudio/profiling/getting-started-with-performance-tools?view=vs-2017) Vincent Torri
