From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) by sourceware.org (Postfix) with ESMTPS id DE7EF3858416 for ; Mon, 17 Jan 2022 15:52:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DE7EF3858416 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-ed1-x52f.google.com with SMTP id z22so67447241edd.12 for ; Mon, 17 Jan 2022 07:52:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HJbYKTBP2ktpaMnwLrCEdcUjA12JDw151CarDYkDYMU=; b=eoJMuXYv70HsB924GrIn7UVsC8klkiY6a3vWKfZv8FbBinYegIzD5Ca84DjN9XUQxr j6KpqhZZhIfRfOnPSLVwmQFvQw+YjddR1H0Lr0YNNIu/zTxHhbz9/iwCQyF6uJ4cbm9f yb5YYGj4s2EON5vqFeQX+j5BQCLI89CeBrDnX5oGGP6mJ1bQO2zLciXRykbo35VAehmW q1NKCKkJtO0LBHfVvcv3mBR+qM/pNQGG4LAOC2v7jiL/yBF55Jw+NbjQ5/5ylSLtmb2S YnIFGeboxgOYuIWpCZcAWScMNP2nBAUrs6QtG/7MtZYMu0BT9j1S5gP4JODVEHx2/ciH 7rXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HJbYKTBP2ktpaMnwLrCEdcUjA12JDw151CarDYkDYMU=; b=c6fiWtpRo6IBUiZRZGEIwkxvBwk5XH7K2zVhcEMdRGTQg8arvai4JxNJg+kWR7RKaN Iq2N4j6tqawfbIUkLrIydjvbHjN30yxEXzZB1h15ljaSJ4y42diMsokXSwK6vfItz0Mk 4rElQYKstUwJQGRY5uvIao8+IwbLT2CPQ2RcMrzcqyShdDIn13W8muAK6Pq+6BD6GWAw R0Bofwzy2kl0Rbat0U6oxOEWZ6JAmqyaF6QqRGcNtqqPxHUmnf+mQ+WVBBzipnb7XkkC +78FVtiE1I8r6D8W/O4LLm6OiVYvoEChbo7xHsbHqD7wpN3qNSNVRtsKeqZwhmrzibQ3 MiqA== X-Gm-Message-State: AOAM532LgG9edpWzycjml+gRgg/VchY1Vzf3ZncYYsOpmde/h0DneHtT F4MuEb1nCG83Thzs0BIpfO7w+QbfXOG41vtQS8A= X-Google-Smtp-Source: ABdhPJwXuwEGJqqadr6dP4ZKZBcNKnLop6xH0wjO+5wQBvSUlDeSIsDUiZ6kNmQNezXqYe7oXZ0StM/hbTkWtXBMIO8= X-Received: by 2002:a05:6402:440f:: with SMTP id y15mr6540809eda.179.1642434720918; Mon, 17 Jan 2022 07:52:00 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: marco atzeri Date: Mon, 17 Jan 2022 16:51:50 +0100 Message-ID: Subject: Re: svn crashes when connection to server refused To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" Cc: "cygwin@cygwin.com" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2022 15:52:03 -0000 On Sun, Jan 16, 2022 at 11:55 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > Hi all, > > Before I go ahead and try to submit this as a bug report with the Apache Subversion project, I wanted to ask > if anybody experiences the same issue as me (or, maybe it's a Cygwin issue, not svn's)... > > I use svn at home on Cygwin via a tunneled connection to my SVN server at work, so when the tunnel is > not up (and basically, svn connects to localhost:SVN-port and supposedly receives "connection refused"), > it crashes ungracefully with SEGFAULT leaving the repo locked ("svn cleanup" is required). When the tunnel > is up, everything goes well. Also, I could not reproduce any such behavior at work, because the server there > is readily available, so the connection always succeeds. > > It's not new, but it reached a tipping point, and I would rather try to have it fixed. > > So this is how it looks like when the tunnel is down: > > $ svn --version > svn, version 1.14.1 (r1886195) > compiled Feb 12 2021, 17:58:10 on x86_64-unknown-cygwin > ... > $ svn up > Updating '.': > Segmentation fault (core dumped) Subversion seems to have along list of upstream issues can you check if the issue was already noted and solved upstream ? If so I can deploy a new release. Regards Marco