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

Re: Reproducible crash in git merge

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 27, 2011, 18:01 UTC
Message-ID
<7vr59s1lzu.fsf@alter.siamese.dyndns.org>
In-Reply-To
<m3pqpcv5ph.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> writes:
Show 6 quoted lines
> David Gilman <davidgilman1@gmail.com> writes:
>
>> Unfortunately I can't share the repo itself because of its contents.
>
> Does anyone remember the script that can be used to anonymize contents
> of repository that cannot be made public for debugging purposes?

That might help in certain narrow other cases, but I suspect that it is a way off tangent in this case, after looking at the stack trace.

The process is dying inside pthe latform implementation of memcpy of inflate from zlib; unless the bug is reproduceable independent of the contents, any modification done by contents anonymizer is very likely to make this particular issue go away, don't you think?

Previous: Jakub NarebskiNext: Jakub Narebski
Message 3 of 5 in “Reproducible crash in git merge”
  1. David GilmanMar 27, 2011
  2. Jakub NarebskiMar 27, 2011
  3. Junio C HamanoMar 27, 2011
  4. Jakub NarebskiMar 29, 2011
  5. David GilmanMar 27, 2011

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.