From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Npkip-0003Cf-1U for garchives@archives.gentoo.org; Thu, 11 Mar 2010 15:54:51 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D2DD5E0A8D; Thu, 11 Mar 2010 15:54:47 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 879F2E0A8D for ; Thu, 11 Mar 2010 15:54:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 242FC1B406E for ; Thu, 11 Mar 2010 15:54:47 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -1.641 X-Spam-Level: X-Spam-Status: No, score=-1.641 required=5.5 tests=[AWL=0.959, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jzHtwmO6E6Y6 for ; Thu, 11 Mar 2010 15:54:39 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by smtp.gentoo.org (Postfix) with ESMTP id C33661B403F for ; Thu, 11 Mar 2010 15:54:38 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NpkiT-0000an-Nc for gentoo-user@gentoo.org; Thu, 11 Mar 2010 16:54:29 +0100 Received: from geodiff-mac3.ulb.ac.be ([164.15.131.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Mar 2010 16:54:29 +0100 Received: from theonewiththeevillook by geodiff-mac3.ulb.ac.be with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Mar 2010 16:54:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Nicolas Richard Subject: [gentoo-user] Re: how to "git-bisect" in a portage-compatible way ? Date: Thu, 11 Mar 2010 16:54:16 +0100 Message-ID: References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: geodiff-mac3.ulb.ac.be User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100308 Thunderbird/3.0.3 In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 46a860c7-8233-4b1b-99df-9388ca633ab5 X-Archives-Hash: 832ff82050eec0b7ae855cb54f0de8a1 Le 10/03/10 17:08, walt a =E9crit : > On 03/10/2010 03:03 AM, Nicolas Richard wrote: >> So the general question is : if I want to use git-bisect (I have never >> done that before, but today is a good time to try), >=20 > It's a great tool and easy to use once you've learned the basic steps. > You can ask here if you need help with it. I have to agree, it's quite a nice tool. Unfortunately the bug is a bit unpredictable (random crash which requires a reboot) and I found out that the version I thought was good (2.4.11) was in fact bad, and that I probably had been lucky not to encounter a crash for some days. Moreover, releases of libdrm prior to 2.4.11 are incompatible with my current xf86-xorg-intel (while writing this and looking at gitk, I notice that there are a few commits which should be compatible. I'll try these later.) What is weird is that if I use older versions, I feel it crashes less often than with new versions. I have in mind two things two try: * bisecting another package, e.g. xf86-xorg-intel or even the kernel. * instead of trying to find a commit which does not have "the" bug, find one which has a related but different bug. I mean, the crash is not always the same, sometimes I can still access the console, sometimes I just have to reboot, sometimes the kernel crashes too... maybe I can find a commit for which the bug behaves differently. Let me stop being off topic for a few seconds, and ask a real question about git-bisect : imagine there are two bugs : bug A is a known bug, present in version 2.4.11 but corrected in 2.4.18, and bug B is another bug which I'm trying to bisect. Problem : they have the same effect (let's say : a crash) and I want to fix bug A because it might hide bug B. Assuming that the patch which fixes bug A can be applied to the files of versions 2.4.11-2.4.18, is it possible to bisect these modified versions ? What I can imagine is : do a normal git-bisect session, but each time apply the patch before ./configure'ing. That sounds ok, but is it ? And if yes, what's the correct way to tell git to "put the changes induced by one commit on the current head" ? (I hope I'm being clear and not mixing the terms, here). > When you configure the git test package, use the "--prefix=3D/usr/local= " > flag so that the test library gets installed in /usr/local/lib, and > /usr/local/include, etc. I followed your advice (/usr/local is actually the default location for libdrm) and it worked quite nice because it is easy to track the files installed by the package within /usr/local... maybe this is not true for more complicated packages ? > Then, to test the new library, just change the /usr/lib/libdrm symlink > to point at /usr/local/lib/libdrm.so.whatever. Actually, it seems that the system first looks in /usr/local/lib before /usr/lib, so it was probably unnecessary to modify the symlinks (noticed it at the end). --=20 Nico.