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

git svn segfaults in _Delta.so

From
Thomas Harning <harningt@gmail.com>
Date
Sep 10, 2008, 18:21 UTC
Message-ID
<E7387B42-6A3D-432B-8478-71A5E510D905@gmail.com>

I just recently setup a new system and installed subversion 1.5.1 and the latest git from head.

On an existing repository (copied from the same system but slightly older software) running git svn rebase will cause it to segfault in _Delta.so (part of subversion's perl libraries).... even when there is nothing to do... it even seems to successfully do all the operations. I've built subversion and git with debugging enabled and cannot get any useful stack-trace. the stacktrace is:

#0 0x00007fbed7edd3a0 in ?? () #1 0x00007fbed99fa75d in ?? () #2 0x0000000000000001 in ?? () #3 0x00007fbed99fb217 in ?? () #4 0x00007fbed99e82d8 in ?? () #5 0x0000000000000001 in ?? () #6 0x000000000070e250 in cwd.17580 () #7 0x000000000070d7f8 in buffer.17586 () #8 0x0000000000f7f408 in ?? () #9 0x00007fbed99fb205 in ?? () #10 0x0000000000000000 in ?? ()

The only way I know that it is _Delta.so is that in 'dmesg' i get: git-svn[1277]: segfault at 7f64fa7213a0 ip 7f64fa7213a0 sp 7fff07a9a2b8 error 14 in _Delta.so[7f64fa92c000+22000]

In another machine w/ very similar software (slightly older by a month or so) I do not see these segfaults. However it is running svn 1.4.6 .. so it might be svn versions... will report on status after downgrade

Next: Thomas Harning
Message 1 of 3 in “git svn segfaults in _Delta.so”
  1. Thomas HarningSep 10, 2008
  2. Thomas HarningSep 10, 2008
  3. Mike HommeySep 10, 2008

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.