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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
