git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug: git crashes on rebase reporting bogus memory corruption

From
DVDaniele Varrazzo <daniele.varrazzo@gmail.com>
Date
Nov 27, 2015, 16:29 UTC
Message-ID
<CA+mi_8ap9676PHKyuK1kdmLm9WLKO3XTUunjF8cwFyULoL=XOw@mail.gmail.com>
In-Reply-To
<CA+mi_8Y5bx-RDCV2oFfFRVZz-Jjcii7QbB6k45B5YsLoed-b8g@mail.gmail.com>

On Fri, Nov 27, 2015 at 2:08 PM, Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:

> Bogus corruption is bogus because I've reproduced it on different machines.
>
> I was trying to rewrite history in a small repos and replace
> indentation tabs with spaces. Steps to reproduce:

Messing up with that repo. Not sure what reportedly originally still works. This should remain as it is:

  git clone -b gitbug https://github.com/dvarrazzo/suponoff.git
  cd suponoff/
  git config core.whitespace
trailing-space,tabwidth=4,tab-in-indent,space-before-tab
  git rebase  6af85bcde9a30c3841b754bbb60c03ba58b88a50 --whitespace=fix
-- Daniele
Previous: Daniele VarrazzoNext: Eric Sunshine
Message 2 of 3 in “Bug: git crashes on rebase reporting bogus memory corruption”
  1. Daniele VarrazzoNov 27, 2015
  2. Daniele VarrazzoNov 27, 2015
  3. Eric SunshineNov 30, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.