From: Greg M <morenzg@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Daniel Stenberg <daniel@haxx.se>, git@vger.kernel.org
Subject: Re: error: git-remote-https died of signal 13
Date: Thu, 24 Apr 2014 08:11:39 -0400 [thread overview]
Message-ID: <CAEHyFQJs2_hMU70ibSe8_k98M6bXrfFWTiHBKcu-473uNhWivQ@mail.gmail.com> (raw)
In-Reply-To: <20140424041504.GA17398@sigill.intra.peff.net>
On Thu, Apr 24, 2014 at 12:15 AM, Jeff King <peff@peff.net> wrote:
> I suspect the curl patch below may fix it:
>
> diff --git a/lib/multi.c b/lib/multi.c
> index bc93264..72e4825 100644
> --- a/lib/multi.c
> +++ b/lib/multi.c
> @@ -1804,10 +1804,13 @@ static void close_all_connections(struct Curl_multi *multi)
>
> conn = Curl_conncache_find_first_connection(multi->conn_cache);
> while(conn) {
> + SIGPIPE_VARIABLE(pipe_st);
> conn->data = multi->closure_handle;
>
> + sigpipe_ignore(conn->data, &pipe_st);
> /* This will remove the connection from the cache */
> (void)Curl_disconnect(conn, FALSE);
> + sigpipe_restore(&pipe_st);
>
> conn = Curl_conncache_find_first_connection(multi->conn_cache);
> }
The patch fixes the problem,
Greg
next prev parent reply other threads:[~2014-04-24 12:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 0:42 error: git-remote-https died of signal 13 Greg M
2014-04-23 6:59 ` Jeff King
2014-04-23 11:49 ` Greg M
2014-04-24 4:15 ` Jeff King
2014-04-24 12:11 ` Greg M [this message]
2014-04-24 12:15 ` Daniel Stenberg
-- strict thread matches above, loose matches on Subject: below --
2013-11-23 16:36 Stefan Beller
2013-11-24 6:54 ` Jeff King
2013-11-24 12:54 ` Stefan Beller
2013-11-24 13:33 ` Jeff King
2013-11-24 15:01 ` Stefan Beller
2013-11-24 15:54 ` Jeff King
2013-11-24 16:13 ` Stefan Beller
2013-11-24 16:32 ` Stefan Beller
2013-11-25 6:39 ` Jeff King
2013-11-25 7:20 ` Daniel Stenberg
2013-11-25 14:32 ` Jeff King
2013-11-25 14:46 ` Jeff King
2013-11-24 22:13 ` Daniel Stenberg
2013-11-24 23:51 ` brian m. carlson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEHyFQJs2_hMU70ibSe8_k98M6bXrfFWTiHBKcu-473uNhWivQ@mail.gmail.com \
--to=morenzg@gmail.com \
--cc=daniel@haxx.se \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).