I think debugging is the number one skill for the average programmer. It implies being quite good at reverse engineering. But as far as debugging is concerned,

I think debugging is the number one skill for the average programmer. It implies being quite good at reverse engineering. But as far as debugging is concerned, it is a must to know: 1) how to reset frame 2) how to set conditional breakpoints 3) do binary search for interesting breakpoint candidates. Going down from a single point isn't very efficient, is better to put a break before and after, then restrict the instruction space by moving them both. That is for non obvious bugs of course Bonus point: use an ide or something to display objects in a custom way (if your language is OO) like IntelliJ allows. And another thing to keep in mind is Sherlock's rule: once everything possible is ruled out, it remains the impossible. Your bug is there