From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: subversion-1.11.1-1+libserf1_0-1.3.9-1: Segfault after failed connect + empty serf debug package
Date: Wed, 01 Jan 2020 17:58:00 -0000 [thread overview]
Message-ID: <1ea5652a-4f9f-051d-e9fa-76e91b375d81@t-online.de> (raw)
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
next reply other threads:[~2020-01-01 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 17:58 Christian Franke [this message]
2020-01-09 17:11 ` David Rothenberger
2020-01-10 17:22 ` David Rothenberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ea5652a-4f9f-051d-e9fa-76e91b375d81@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).