Difference between gdb, valgrind, strace, ltrace and apport

debugging gdb valgrind strace ltrace
Det picture Det · Apr 7, 2013 · Viewed 9.6k times · Source

I'm looking for the difference between the following debugging tools.

What are those?

E: On the off chance that somebody stumbles in here and was wondering about the same thing the "differences" are (shortened from the man pages):

  • GDB

    Allows you to see what's going on "inside" a program while it runs/crashed.

  • Valgrind

    A flexible series of tools for debugging and profiling.

  • Strace

    Records/intercepts system calls which are called/received by a process.

  • Ltrace

    Records/intercepts signals/dynamic library/system calls which are called/received by a process.

  • Apport

    Intercepts crashes/unhandled exceptions, collects OS information, presents a helpful UI, and is able to file non-crash bugs.

Answer

Related questions

How do I analyze a program's core dump file with GDB when it has command-line parameters?

My program operates like this: exe -p param1 -i param2 -o param3 It crashed and generated a core dump file, core.pid. I want to analyze the core dump file by gdb ./exe -p param1 -i param2 -o param3 core.…

Read More
How do I print the full value of a long string in gdb?

I want to print the full length of a C-string in GDB. By default it's being abbreviated, how do I force GDB to print the whole string?

Read More
How do I pass a command line argument while starting up GDB in Linux?

I have to debug a program that has errors in it as part of my assignment. However, I must first pass command line arguments in order to solve this problem. I do: gdb -tui InsertionSortWithErrors which works, but after that …

Read More