ltrace VS Valgrind

ltrace mentions (0)

Valgrind mentions (28)

• Why So Slow? Using Profilers to Pinpoint the Reasons of Performance Degradation

  First, we used Callgrind to get some results. Using Callgrind massively slowed down the execution. In some cases, it was almost 20 times slower than the unprofiled version. Callgrind is based on Valgrind, which uses dynamic binary instrumentation to inspect and control different aspects of applications, causing a significant slowdown. We used KCachegrind to interpret and visualize the reports generated by... - Source: dev.to / 3 days ago

• trouble fixing memory leak in C..

  If you post your actual code, somebody might be able to help you spot the problem. You could also try running your program under a memory checker like Valgrind. Or you could just add debug logs with the addresses of the objects that you're allocating/freeing, so that you can track down where they don't match up. - Source: Reddit / 3 months ago

• [C] program which lists all files in a directory recursively

  A memory checker like Valgrind can help you by automatically identifying issues like this. - Source: Reddit / 4 months ago

• Concatenating two linked lists

  In addition to a debugger, you can use a memory checker like Valgrind to more precisely narrow down the source of illegal memory accesses. - Source: Reddit / 4 months ago

• What could cause a program to not work in debug mode, but release mode works just fine?

  Since everyone else has gone into great detail, now is a good time to learn about Valgrind (specifically memcheck). It can help you find memory-based issues with your code. - Source: Reddit / 4 months ago