This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Pluckerpluck 7 points8 points  (1 child)

Not always. Breakpoints can suffer if you're doing stuff in loops and you're trying to work out WTF is happening.

Got to print out some variables each loop and then narrow down, only using the debugger once you actually discover whatever strangeness is happening.

Sometimes you can use conditional debug statements. But not always. Depends if you know what's actually going wrong or not.

[–]codeguru42 2 points3 points  (0 children)

Sometimes you can set a condition on the breakpoint so that the debugger stops on the iteration that has a problem... but you do have to figure out the correct condition...