Software Alternatives & Reviews

ltrace VS Valgrind

Compare ltrace VS Valgrind and see what are their differences

ltrace logo ltrace

ltrace intercepts and records dynamic library calls which are called by an executed process and the...

Valgrind logo Valgrind

Valgrind is an instrumentation framework for building dynamic analysis tools.
ltrace Landing Page
ltrace Landing Page
Valgrind Landing Page
Valgrind Landing Page

ltrace details

Monitoring Tools OS & Utilities Log Management

Valgrind details

OS & Utilities Resource Profiling And Monitoring Monitoring Tools

ltrace videos

How to Spy on Running Programs (strace, ltrace)

More videos:

  • Review - Sudo ltrace | Ryan's CTF [15] Strings wont help you

Valgrind videos

Detecting Memory Leaks With Valgrind

More videos:

  • Review - Finding memory errors with Valgrind
  • Review - sparcv9 New architecture to be supported by Valgrind

Category Popularity

0-100% (relative to ltrace and Valgrind)

Social recommendations and mentions

Based on our record, Valgrind seems to be more popular. It has been mentiond 28 times since March 2021. We are tracking product recommendations and mentions on Reddit, HackerNews and some other platforms. They can help you identify which product is more popular and what people think of it.

ltrace mentions (0)

We have not tracked any mentions of ltrace yet. Tracking of ltrace recommendations started around Mar 2021.

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: / 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
View more

What are some alternatives?

When comparing ltrace and Valgrind, you can also consider the following products

strace - Trace system calls and signals. A diagnostic, debugging and instructional userspace utility.

API Monitor - API Monitor is a software that monitors and displays API calls made by applications and services. Its a powerful tool for seeing how Windows and other applications work or tracking down problems that you have in your own applications

ftrace - A function tracer for the Linux kernel.

perf - Perf is a simple app monitoring solution paired with meaningful alerts.

Kcachegrind - Callgrind is a profiling tool and KCachegrind is able to visualize output of the profilers.

DTrace - DTrace is a performance analysis and troubleshooting tool for Solaris, Mac OS X and FreeBSD.

User reviews

Share your experience with using ltrace and Valgrind. For example, how are they different and which one is better?
Log in or Post with