git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: segfault in git-remote-http

From
Jeff King <peff@peff.net>
Date
Apr 10, 2013, 18:51 UTC
Message-ID
<20130410185114.GA18084@sigill.intra.peff.net>
In-Reply-To
<20130410090850.bacd762ad52eb3643ca99927@lavabit.com>
On Wed, Apr 10, 2013 at 09:08:50AM -0700, rh wrote:
Show 10 quoted lines
> > which should show both program names. Git invokes git-remote-* based
> > on the URL you fed it. So if you are seeing a segfault in
> > git-remote-http, presumably you fed it an http URL (which may still
> > execute SSL code if it redirects to an https URL).
> 
> Here's the command I ran (from initial post):
> git clone https://github.com/bitcoin/bitcoin.git
> 
> This returns no error on the command line and produced the segfault
> reported by the kernel. git clone returns immediately.

It does correctly report a failed exit code. The lack of message is because git assumes that the helper will produce a useful message before dying, but obviously it doesn't. There's already a patch[1] to fix this, but it hasn't been merged yet.

As for why dmesg reports git-remote-http, I'm not sure. If you "strace -f" the command, you can see that git is running git-remote-https. Why the kernel chooses to report "git-remote-http", I don't know; you'd have to look into how the kernel makes that decision. But I doubt it is related to the reason for the segfault in the first place.

-Peff
Previous: rhNext: Jeff King
Message 12 of 17 in “segfault in git-remote-http”
  1. rhApr 7, 2013
  2. rhApr 7, 2013
  3. rhApr 9, 2013
  4. Jeff KingApr 9, 2013
  5. Daniel StenbergApr 9, 2013
  6. rhApr 12, 2013
  7. rhApr 9, 2013
  8. Jeff KingApr 9, 2013
  9. rhApr 9, 2013
  10. Jeff KingApr 10, 2013
  11. rhApr 10, 2013
  12. Jeff KingApr 10, 2013
  13. Jeff KingApr 10, 2013
  14. rhApr 10, 2013
  15. rhApr 13, 2013
  16. rhApr 10, 2013
  17. Jeff KingApr 10, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.