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

Re: segfault in git-remote-http

From
Rrh <richard_hubbe11@lavabit.com>
Date
Apr 7, 2013, 16:42 UTC
Message-ID
<20130407094234.a5b85a2af838c8d7eabbad49@lavabit.com>
In-Reply-To
<20130407093812.cae0e19123f7b6d2061800aa@lavabit.com>
git version 1.7.12.1

On Sun, 7 Apr 2013 09:38:12 -0700 rh <richard_hubbe11@lavabit.com> wrote:

Show 20 quoted lines
> Hello,
> (cross-posting to bitcoin-devel in case they've seen it)
>  
> 1) git clone https://github.com/bitcoin/bitcoin.git
> segfaulted in libcrypto.so.1.0.0
> 
> 2) git clone git://github.com/bitcoin/bitcoin.git
> had no problems
> 
> This was yesterday, I retried today
> 
> 3) git clone https://github.com/bitcoin/bitcoin.git
> and it worked fine.
> 
> Yesterday I was running bitcoin-0.8.1-linux/bitcoin-qt when #1 failed.
> Today I was running bitcoind when I ran #3
> 
> Two things I thought might be coming into play here, network
> pressure and memory pressure. Is this occurence reasonably
> possible or is something else afoot?
Previous: rhNext: rh
Message 2 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.