From: Andreas Schwab <schwab@linux-m68k.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Odd git overrflow bug?
Date: Sun, 10 Jul 2016 20:41:07 +0200 [thread overview]
Message-ID: <87eg712v5o.fsf@linux-m68k.org> (raw)
In-Reply-To: <CA+55aFz=sZnABJr6F2yF_xvx6J6fZod6BbiL2OwszEnjjn-dEw@mail.gmail.com> (Linus Torvalds's message of "Sun, 10 Jul 2016 09:02:44 -0700")
Linus Torvalds <torvalds@linux-foundation.org> 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@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-07-10 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 16:02 Odd git overrflow bug? Linus Torvalds
2016-07-10 18:41 ` Andreas Schwab [this message]
2016-07-10 21:01 ` Linus Torvalds
2016-07-10 21:05 ` Linus Torvalds
2016-07-10 21:21 ` Linus Torvalds
2016-07-10 21:29 ` Linus Torvalds
2016-07-10 21:52 ` Junio C Hamano
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=87eg712v5o.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.