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

Re: Seg Fault on git fetch with fetch.negotiationAlgorithm=skipping

From
Son Luong Ngoc <sluongng@gmail.com>
Date
May 1, 2020, 08:13 UTC
Message-ID
<BFB84B3B-FB39-4217-A6C6-7599F6F755E2@gmail.com>
In-Reply-To
<20200430202014.GB2014@syl.local>
Hi Taylor,
Show 5 quoted lines
> On Apr 30, 2020, at 22:20, Taylor Blau <me@ttaylorr.com> wrote:
> 
> Are you able to share a core file? If not, it would be very helpful for
> you to 'git fast-export --anonymize ...' and see if you can reproduce
> the problem on an anonymized copy of your repository.

I played a bit with --anonymized yesterday but export/import is slow and I still need to review the history to see whether it could be released.

It might take more time than just a few days.
> I can speculate about the cause of the crash from your strace above, but
> a core file would be more helpful.

I have added perf trace2 in https://gist.github.com/sluongng/e48327cc911c617ed2ef8578acc2ea34#file-perf-trace2-L52 (git version is 2.26.2)

I think this trace is a lot cleared than the strace log.
> Thanks,
> Taylor

Cheers, Son Luong.

Previous: Taylor BlauNext: Taylor Blau
Message 3 of 4 in “Seg Fault on git fetch with fetch.negotiationAlgorithm=skipping”
  1. Son Luong NgocApr 30, 2020
  2. Taylor BlauApr 30, 2020
  3. Son Luong NgocMay 1, 2020
  4. Taylor BlauMay 1, 2020

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.