From: "H.J. Lu" <hjl.tools@gmail.com>
To: Binutils <binutils@sourceware.org>, GDB <gdb@sourceware.org>
Subject: Does "git bisect" work for anyone?
Date: Fri, 2 Oct 2020 15:25:14 -0700 [thread overview]
Message-ID: <CAMe9rOp0UfUtqb=n0SzT4AKxOFhihpGPEBpPfGOHDUxsZKU2zw@mail.gmail.com> (raw)
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.
next reply other threads:[~2020-10-02 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 22:25 H.J. Lu [this message]
2020-10-03 6:27 ` Andreas Schwab
2020-10-03 13:57 ` H.J. Lu
2020-10-06 21:29 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMe9rOp0UfUtqb=n0SzT4AKxOFhihpGPEBpPfGOHDUxsZKU2zw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).