Edmundo Carmona Antoranz <eantor...@gmail.com> wrote:
> 1 [main] perl 5652 cygwin_exception::open_stackdumpfile: Dumping stack
> trace to perl.exe.stackdump
> 
> And then, in the file:
> 
> Exception: STATUS_ACCESS_VIOLATION at rip=0048360C10C
> rax=0000000601E4BFF8 rbx=000000005219E248 rcx=000000060003A590
> rdx=0000000000000000 rsi=000000000000A950 rdi=0000000000000004
> r8 =0000000000000000 r9 =0000000000000000 r10=0000000000230000
> r11=000000048D78607A r12=0000000000000003 r13=000006FFFFF54A98
> r14=0000000601E18030 r15=000006FFFFF54AB0
> rbp=0000000000054A88 rsp=000000000022B810
> program=C:\Program Files\Git\usr\bin\perl.exe, pid 5652, thread main
> cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B

Any chance you can reproduce this on a Linux system?
I do not use non-Free systems and have no debugging experience
there at all.

> With my very flawed knowledge of perl I have seen that the process is
> getting to Ra.pm around here:

It could also be a bug in the SVN bindings or the port of
Perl.  Which versions are you running?


I've also been wondering about the motivation of SVN developers to do a
good job on maintaining their Perl bindings (given git-svn is likely the
main user of them).
We've certainly had problems in the past with SVN breaking and
causing git-svn to segfault around 2011-2012; but it's been a while...
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to