[FFmpeg-devel] Help with git bisect

[Michael Niedermayer]

On Wed, May 11, 2011 at 05:22:29PM +0000, Jon Drukman wrote:
> I've found a bug in the current version of ffmpeg.  Certain files cause the mp4
> muxer to go bonkers and fail.  (See http://ffmpeg.org/trac/ffmpeg/ticket/187)
> I'm trying to isolate the commit that caused it but I don't really know how to
> use git bisect.  You're supposed to provide the tag of the last known good
> version, but I have no idea what that might be.  Are there even tagged releases?
>  How do I tell it to bisect the entire history of the repository?  Do I have to
> make distclean or clean in between checkouts?
> 
> I've done:
> 
> git bisect start
> git bisect bad master
> 
> but now I have to provide git bisect good <something> and I don't know what
> <something> is.  The last working version of ffmpeg I have is from the svn days,
> built in August 2010.  I would have stuck with that but there's a bug in the wmv
> decoder that seems to be better in the current repo.

if your known good svn revission is r12345
git log --grep="revision 12345"

    commit 9822564d1d66d9202bfec3fa78a93243963768dc
    Author: Aurelien Jacobs <aurel at gnuage.org>
    Date:   Wed Mar 5 21:43:30 2008 +0000

        make compilation of mpeg12* and mpegvideo conditional

        Originally committed as revision 12345 to svn://svn.ffmpeg.org/ffmpeg/trunk
-----
to check that revission out
git checkout 9822564d1d66d9202bfec3fa78a93243963768dc
and once you tested that it works
git bisect good 9822564d1d66d9202bfec3fa78a93243963768dc


[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I know you won't believe me, but the highest form of Human Excellence is
to question oneself and others. -- Socrates
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20110511/f343a64e/attachment.asc>