Bisecting bugs with Git

Often when reporting bugs encountered with projects such as Mesa or Linux kernel, a user may be asked to bisect between the last known version that worked for them and the newer version which is causing them problems in order to see what is the troublesome commit. On Arch this can be done fairly trivially thanks to the functionality of the AUR.

Reverting to an older release

It might be useful to confirm that it is the new package release that is causing the problem. Downgrading packages on Arch can be accomplished trivially as long as an older version of the package is still stored as cache on your system, or you can use Arch Linux Archive.

Note: Even if the older version fixes the problem it is still possible that is not a bug within the program, but a problem with the packages as provided by Arch.

Building package from git

In order to bisect we are going to need to build a version of package from git. This can be accomplished by building the -git package from the AUR.

Setting up the bisect

Once package is successfully built you need to change into the git root directory in the src/ directory. The name of the git root directory is often the same as pkgname (or without the -git suffix):

$ cd src/git_root

From there you can start the process of bisecting:

$ git bisect start

The following command will show you all the tags you can use to specify where to bisect:

$ git tag

Following on from the earlier example, we will assume that the version oldver worked for us while newver did not:

$ git bisect good oldver
$ git bisect bad newver

Now that we have our good and bad versions tagged we can proceed to test commits.

Bisecting

Change back into the directory with the PKGBUILD. If you are still in the directory mentioned in the previous section this can be accomplished like so:

$ cd ../..

You can now rebuild and install the specific revision of the package:

$ makepkg -efsi

Note: It is very important to keep the -e prefix intact as otherwise it will remove all the changes you have made.

Once the new package is installed you can test for your previously discovered error. Return to the directory you were in the previous section:

$ cd src/git_root

If you encountered your problem, tell that the revision was bad:

$ git bisect bad

If you did not encounter your problem, tell that the revision it was good:

$ git bisect good

Then do as described at the beginning of this section again and repeat until git bisect names the troublesome commit.

Note:

• You may need to run a make clean after issuing the git bisect command.
• It will actually count down the number of steps all the way down to zero, so it is important not to stop until it actually names the first bad commit.

Speeding up builds

Building smaller kernel

You can shorten kernel build times by building only the modules required by the local system using modprobed-db, or by make localmodconfig. Of course you can completely drop irrelevant drivers, for example sound drivers to debug a network problem.

Ccache

If you are bisecting a large project built using gcc, it might be possible to reduce build times by enabling ccache. It may take several build iterations before you start to see benefits from the cache, however. The likelihood of cache hits generally increases as the distance between bisection points decreases.

Note: Ccache is effective only when compiling exactly identical sources. And to bisect the kernel, it is not necessary to do make clean, meaning ccache is a complete waste.

Restoring package

Reverting to an original version of the package can be done by installing the package from repositories with pacman.

See also

• Fighting regressions with git bisect
• git-bisect(1)
• Gentoo:Kernel git-bisect