Does "git bisect" work for anyone?

[H.J. Lu]

On master branch, I got

$ git checkout d0e70c4189d5d6a6e63b85c1d3c10c74852173b4
Previous HEAD position was 5a805384b83 asan: readelf buffer overflow and abort
HEAD is now at d0e70c4189d Automatic date update in version.in
$ git bisect good
$ git checkout fe07b5721a64a84e36ec63e15638b87655faf1bf
Previous HEAD position was d0e70c4189d Automatic date update in version.in
HEAD is now at fe07b5721a6 gdb/testsuite: Update test pattern in
ptype-on-functions.exp
$ git bisect bad
Some good revs are not ancestors of the bad rev.
git bisect cannot work properly in this case.
Maybe you mistook good and bad revs?


-- 
H.J.