Writing a Linux Debugger Part 6: Source-level stepping
A couple of posts ago we learned about DWARF information and how it lets us relate the machine code to the high-level source. This time we’ll be putting this knowledge into practice by adding source-level stepping to our debugger.
These links will go live as the rest of the posts are released.
- Registers and memory
- Elves and dwarves
- Source and signals
- Source-level stepping
- Source-level breakpoints
- Stack unwinding
- Handling variables
- Next steps
Exposing instruction-level stepping
But we’re getting ahead of ourselves. First let’s expose instruction-level single stepping through the user interface. I decided to split it between a
single_step_instruction which can be used by other parts of the code, and a
single_step_instruction_with_breakpoint_check which ensures that any breakpoints are disabled and re-enabled.
As usual, another command gets lumped into our
With these functions added we can begin to implement our source-level stepping functions.
Implementing the steps
We’re going to write very simple versions of these functions, but real debuggers tend to have the concept of a thread plan which encapsulates all of the stepping information. For example, a debugger might have some complex logic to determine breakpoint sites, then have some callback which determines whether or not the step operation has completed. This is a lot of infrastructure to get in place, so we’ll just take a naive approach. We might end up accidentally stepping over breakpoints, but you can spend some time getting all the details right if you like.
step_out, we’ll just set a breakpoint at the return address of the function and continue. I don’t want to get into the details of stack unwinding yet – that’ll come in a later part – but it suffices to say for now that the return address is stored 8 bytes after the start of a stack frame. So we’ll just read the frame pointer and read a word of memory at the relevant address:
remove_breakpoint is a little helper function:
step_in. A simple algorithm is to just keep on stepping over instructions until we get to a new line.
step_over is the most difficult of the three for us. Conceptually, the solution is to just set a breakpoint at the next source line, but what is the next source line? It might not be the one directly succeeding the current line, as we could be in a loop, or some conditional construct. Real debuggers will often examine what instruction is being executed and work out all of the possible branch targets, then set breakpoints on all of them. I’d rather not implement or integrate an x86 instruction emulator for such a small project, so we’ll need to come up with a simpler solution. A couple of horrible options are to just keep stepping until we’re at a new line in the current function, or to just set a breakpoint at every line in the current function. The former would be ridiculously inefficient if we’re stepping over a function call, as we’d need to single step through every single instruction in that call graph, so I’ll go for the second solution.
This function is a bit more complex, so I’ll break it down a bit.
at_high_pc are functions from
libelfin which will get us the low and high PC values for the given function DIE.
We’ll need to remove any breakpoints we set so that they don’t leak out of our step function, so we keep track of them in a
std::vector. To set all the breakpoints, we loop over the line table entries until we hit one which is outside the range of our function. For each one, we make sure that it’s not the line we are currently on, and that there’s not already a breakpoint set at that location.
Here we are setting a breakpoint on the return address of the function, just like in
Finally, we continue until one of those breakpoints has been hit, then remove all the temporary breakpoints we set.
It ain’t pretty, but it’ll do for now.
Of course, we also need to add this new functionality to our UI:
Testing it out
I tested out my implementation with a simple program which calls a bunch of different functions:
You should be able to set a breakpoint on the address of
main and then in, over, and out all over the program. Expect things to break if you try to step out of
main or into some dynamically linked library.
You can find the code for this post here. Next time we’ll use our newfound DWARF expertise to implement source-level breakpoints.
Let me know what you think of this article on twitter @TartanLlama or leave a comment below!