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

Re: SEGV in git-apply

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 20, 2007, 02:14 UTC
Message-ID
<Pine.LNX.4.63.0701200312000.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20070120014851.GF5231@admingilde.org>
Hi,
On Sat, 20 Jan 2007, Martin Waitz wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x080500fa in apply_patch (fd=5, filename=0xbf821b4d "/tmp/404241.patch",
>     inaccurate_eof=<value optimized out>) at builtin-apply.c:2504
> 2504                    if (pathlen <= prefix_length ||

It seems that the culprit is not this line (you have an optimized binary, so that is expected).

My guess is that your patch does not contain a new name, neither an old name.

It could also be that the filename has length 0.
But without that patch I cannot tell.

Ciao, Dscho

Previous: Martin WaitzNext: Martin Waitz
Message 2 of 7 in “SEGV in git-apply”
  1. Martin WaitzJan 20, 2007
  2. Johannes SchindelinJan 20, 2007
  3. Martin WaitzJan 20, 2007
  4. apply --cached: fix crash in subdirectoryJohannes Schindelin, Jan 21, 2007
  5. Martin WaitzJan 21, 2007
  6. Rogan DawesJan 21, 2007
  7. Johannes SchindelinJan 21, 2007

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.