Subversion segfaults with null instruction pointer after a failed
connect. This affects the http and https protocols but not the svn protocol.
Related report: https://cygwin.com/ml/cygwin/2019-11/msg00126.html
Testcase:
$ uname -srvmo
CYGWIN_NT-10.0 3.1.2(0.340/5/3) 2019-12-21 15:25 x86_64 Cygwin
$ cygcheck -f /bin/svn
subversion-1.11.1-1
$ cygcheck -f /bin/cygserf-1-0.dll
libserf1_0-1.3.9-1
$ svn info https://127.0.0.1:49494
Segmentation fault (core dumped)
$ svn info http://127.0.0.1:49494
Segmentation fault (core dumped)
$ svn info svn://127.0.0.1:49494
svn: E170013: Unable to connect to a repository at URL
'svn://127.0.0.1:49494'
svn: E000111: Can't connect to host '127.0.0.1': Connection refused
Stacktrace from gdb:
#0 0x0000000000000000 in ?? ()
#1 0x00000003ce7c2c87 in serf.process_connection () from
/usr/bin/cygserf-1-0.dll
#2 0x00000003ce7c1333 in serf_event_trigger () from
/usr/bin/cygserf-1-0.dll
#3 0x00000003ce7c141c in serf_context_run () from /usr/bin/cygserf-1-0.dll
#4 0x00000003ce0e7a11 in svn_ra_serf__context_run (sess=0x8000c2fb8,
waittime_left=0xffffbef0, scratch_pool=0x8000d7e38)
at
/usr/src/debug/subversion-1.11.1-1/subversion/libsvn_ra_serf/util.c:913
...
Is possibly some error handling function pointer not set properly?
Same problem applies to cygwin x86 version. Downgrading to
cygwin-3.0.7-1, libserf1_0-1.3.8-1 and subversion-1.10.4-1 does not help.
There is no easy way for further debugging. A serf-debuginfo package
exists, but its tarball is empty...
PS: On the mirrors, there is still a serf-1.2.1-1-src.tar.bz2 with a
(nonempty!) serf-debuginfo-1.2.1-1.tar.bz2 but the corresponding binary
package libserf1_0-1.2.1-1.tar.xz is missing.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
