GDB function call tracing

Question

Is there a way to attach a print statement to the call of a function? I would like to debug a x64 program with nested loops and logic and it would be faster to see the sequence of function calls by printing them as they occur, rather than setting breakpoints.

Can this be done with a post hook in gdb or a different technique?

Employed Russian · Accepted Answer · 2018-11-23 17:36:45Z

2

Is there a way to attach a print statement to the call of a function?

Yes: attach a breakpoint to every function you want to trace, and attach commands to each of these breakpoints:

(gdb) break foo
(gdb) commands $bpnum
continue
end

Now every time foo is called, GDB will print the usual "Breakpoint N ..." message, and then continue.

Obviously you could print additional info (argument values, call stack, thread-id, etc.).

You will probably want to set height 0 to disable pagination. You will also probably want to log this to a file (see set logging file, set logging on, etc.)

answered Nov 23, 2018 at 17:36

Employed Russian

217k36 gold badges324 silver badges396 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

GDB function call tracing

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related