public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Fri, 10 Jan 2020 17:22:00 -0000	[thread overview]
Message-ID: <8bc0caef-4ed6-29f3-28fc-2cef71d4ded1@acm.org> (raw)
In-Reply-To: <7f520d87-a09d-f93e-56f8-545b1968fffb@acm.org>

On 1/9/2020 9:11 AM, David Rothenberger wrote:
> 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 was able to build the latest subversion 1.13 and unfortunately, the
issue still exists in that version. I tried installing an unstripped
version of the serf library, but I still could not get a full backtrace.
There is no update to serf.

At this point, I don't have any further ideas to troubleshoot this.


-- 
David Rothenberger  ----  daveroth@acm.org

The most dangerous organization in America today is:
        (a) The KKK
        (b) The American Nazi Party
        (c) The Delta Frequent Flyer Club

--
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

      reply	other threads:[~2020-01-10 17:22 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
2020-01-10 17:22   ` David Rothenberger [this message]

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=8bc0caef-4ed6-29f3-28fc-2cef71d4ded1@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).