From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: Re: subversion-1.11.1-1+libserf1_0-1.3.9-1: Segfault after failed connect + empty serf debug package
Date: Thu, 09 Jan 2020 17:11:00 -0000 [thread overview]
Message-ID: <7f520d87-a09d-f93e-56f8-545b1968fffb@acm.org> (raw)
In-Reply-To: <1ea5652a-4f9f-051d-e9fa-76e91b375d81@t-online.de>
On 1/1/2020 9:57 AM, Christian Franke wrote:
> 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
I can reproduce this issue, but I don't anticipate investigating it.
I have yet to package the latest Subversion release. I no longer use
Subversion and the build process is quite complicated. Maintaining the
Cygwin port has always been near the limits of my abilities, and since I
no longer use Subversion, I've simply lost interest.
If you would like to take over maintenance of Subversion, I'd be happy
to support you as much as I can. ;-)
> There is no easy way for further debugging. A serf-debuginfo package
> exists, but its tarball is empty...
serf switched to scons as a build platform. scons is written in Python
and aims to replace autoconf/automake. scons knew nothing about Cygwin
when serf switched to it, so I had to teach it to build Cygwin stuff. I
am NOT a Python programmer, but I managed to get it working. Well,
everything except the debug packages.
If you know Python, please have a try fixing it.
Otherwise, you can rebuild serf from source with debugging enabled and
without stripping the symbols. There's a section of the .cygport file
commented out to do this.
--
David Rothenberger ---- daveroth@acm.org
Hain't we got all the fools in town on our side? And hain't that a big
enough majority in any town?
-- Mark Twain, "Huckleberry Finn"
--
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 prev parent reply other threads:[~2020-01-09 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 17:58 Christian Franke
2020-01-09 17:11 ` David Rothenberger [this message]
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=7f520d87-a09d-f93e-56f8-545b1968fffb@acm.org \
--to=daveroth@acm.org \
--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).