Re: Real-life kernel debugging scenario
- From
- David Lang <david.lang@digitalinsight.com>
- Date
- Nov 8, 2005, 00:59 UTC
- Message-ID
- <Pine.LNX.4.62.0511071657030.9339@qynat.qvtvafvgr.pbz>
- In-Reply-To
- <dkosr7$f4s$1@sea.gmane.org>
On Mon, 7 Nov 2005, walt wrote:
Show 5 quoted lines
> My worry: what happens when I'm not smart enough to guess > which developer to email? My first instinct is to back out > the most recent commits one-by-one until the bug goes away. > > First: is this an optimal tactic?
it will work, but it's not optimal. this is exactly what git bisect is designed for.
you tell it that the prior night's version was good and the current version is bad. It picks a version 'halfway' in between the two and you test that. tell git if the test failed or not and it will then give you the next one to try. repeat until you identify exactly which commit triggers the problem.
unfortunantly I can't trivially point you at the right place in the docs.
David Lang
-- There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies. -- C.A.R. Hoare