Re: Odd git overrflow bug?

From: Andreas Schwab <schwab@linux-m68k.org>
Date: Jul 10, 2016, 18:41 UTC
Message-ID: <87eg712v5o.fsf@linux-m68k.org>
In-Reply-To: <CA+55aFz=sZnABJr6F2yF_xvx6J6fZod6BbiL2OwszEnjjn-dEw@mail.gmail.com>

Linus Torvalds <torvalds@linux-foundation.org> writes:

Show 8 quoted lines

> We have an odd bug report in the kernel, where somebody had trouble
> bisecting all the way due to
>
>   "git is failing with "you are trying to use to much memory"(?!)"
>
> which can't be an exact  error message quote, but the closest I can
> find smells like the "unsigned_add_overflows()" check in the strbuf
> code. Very odd.

I've seen that too, but only at the end of bisection, when it tries to display the bad commit.

For example, when running git bisect on git://gcc.gnu.org/git/gcc:

$ git bisect start de4fa746271d39d490b59bdfbbdd2cf5b54c0521 dd58bf212e9a250300e64d78748418b01d0035cd
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[f529d395184700e2404f4a293a2198355ab7ded5] Daily bump.
$ git bisect good
de4fa746271d39d490b59bdfbbdd2cf5b54c0521 is the first bad commit
commit de4fa746271d39d490b59bdfbbdd2cf5b54c0521
fatal: you want to use way too much memory

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."