2 ms·
debug by bisection is one of those things which I think only occur in some projects. The ones which do atomic commit (or near atomic, at least atomic to the pro
by ggm 4y ago
debug by bisection is one of those things which I think only occur in some projects. The ones which do atomic commit (or near atomic, at least atomic to the problem intent of the commit) -If you fold 100 updates to random codepoints in one commit, bisection only delivers limited help. How do you unwind the interrelated changes, possibly in one file? So if the style is to stack up edits, save, commit, move on, you will never do this.
it's a fantastic tool, but if you are chasing a kernel bug in an OS, its intensely time consuming to do, without the local clone of the repo to walk back the atomic(ish) changes and my lived reality is the kernel re-make is a lot slower than you want because imputed dependency chains typically re-compile a LOT more than you think.
I would not be surprised if duck debugging and printf() yields the outcome faster than what is (forgive loaded language) blame-finger pointing, sometimes.
It unquestionably works. It is not low-cost. The goal of preserving it is worthy. This is sensible.