Re: segfault in git-remote-http

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

> 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?
> 

The symptoms that this patch addresses look similar:

http://article.gmane.org/gmane.mail.postfix.user/217790

Quote from that thread:
"This behavior is actually documented (SSL_set_fd() destroys
a BIO already on the SSL handle, and creates a new BIO)."

Maybe someone used to looking at git-remote-http code can
say anything about this.

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]