Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes: > 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@xxxxxxxxxxxxxx GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html