From: marco atzeri <marco.atzeri@gmail.com>
To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: svn crashes when connection to server refused
Date: Mon, 17 Jan 2022 16:51:50 +0100 [thread overview]
Message-ID: <CAB8Xom-ZMzuP_w-_QOZa5pnfjgwF-R-GoOg0ad5hfNXnyTyqDA@mail.gmail.com> (raw)
In-Reply-To: <DM8PR09MB7095066A2A454A6D3EA2C98CA5569@DM8PR09MB7095.namprd09.prod.outlook.com>
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
next prev parent reply other threads:[~2022-01-17 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 22:55 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-17 15:51 ` marco atzeri [this message]
2022-01-18 2:03 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-18 6:15 ` Marco Atzeri
2022-01-18 17:31 ` Brian Inglis
2022-01-18 19:30 ` Marco Atzeri
2022-01-18 8:35 ` Brian Inglis
2022-01-26 20:16 ` Andrey Repin
2022-01-26 21:05 ` Marco Atzeri
2022-01-28 8:01 ` Andrey Repin
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=CAB8Xom-ZMzuP_w-_QOZa5pnfjgwF-R-GoOg0ad5hfNXnyTyqDA@mail.gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=lavr@ncbi.nlm.nih.gov \
/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).