Bug 200934 - git-remote-https core dump on FreeBSD 9.3-RELEASE
Summary: git-remote-https core dump on FreeBSD 9.3-RELEASE
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Renato Botelho
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-17 15:22 UTC by a.ulasov
Modified: 2015-07-15 12:28 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description a.ulasov 2015-06-17 15:22:17 UTC
I get git-remote-https.core, when I try to clone remote repository via HTTPS on FreeBSD 9.3 amd64
# pkg info -d git
git-2.4.2:
        expat-2.1.0_2
        openssl-1.0.2_3
        curl-7.42.1_1
        gettext-runtime-0.19.4
        libiconv-1.14_8

Backtrace output:
#0  0x00000008010f4ac4 in engine_unlocked_finish () from /usr/local/lib/libcrypto.so.8
[New Thread 803c07400 (LWP 104977/git-remote-https)]
(gdb) bt
#0  0x00000008010f4ac4 in engine_unlocked_finish () from /usr/local/lib/libcrypto.so.8
#1  0x00000008010f4ba1 in ENGINE_finish () from /usr/local/lib/libcrypto.so.8
#2  0x0000000801108099 in EVP_DigestInit_ex () from /usr/local/lib/libcrypto.so.8
#3  0x00000008020594b0 in ssl23_connect () from /usr/lib/libssl.so.6
#4  0x000000080166e75c in curl_slist_free_all () from /usr/local/lib/libcurl.so.4
#5  0x00000000006e8800 in ?? ()
#6  0xadf6102000000002 in ?? ()
#7  0x0000000000000004 in ?? ()
#8  0x00007fffffffe010 in ?? ()
#9  0x00000000000493e0 in ?? ()
#10 0x0000000000000000 in ?? ()

I've server with FreeBSD 10.1-RELEASE and there is no problem with repository cloning via HTTPS.
I found that the source of the problem is /usr/lib/libssl.so.6

This library is needed for /usr/local/lib/libcurl.so.4
When libcurl.so.4 built with libssl.so.7 (FreeBSD 10) theris no problem.

#ldd /usr/local/lib/libcurl.so.4      
/usr/local/lib/libcurl.so.4:
        libssl.so.6 => /usr/lib/libssl.so.6 (0x801266000)
        libheimntlm.so.10 => /usr/lib/libheimntlm.so.10 (0x8014bd000)
        libhx509.so.10 => /usr/lib/libhx509.so.10 (0x8016c2000)
        libcom_err.so.5 => /usr/lib/libcom_err.so.5 (0x801903000)
        libcrypto.so.6 => /lib/libcrypto.so.6 (0x801b05000)
        libasn1.so.10 => /usr/lib/libasn1.so.10 (0x801ead000)
        libroken.so.10 => /usr/lib/libroken.so.10 (0x802131000)
        libcrypt.so.5 => /lib/libcrypt.so.5 (0x802343000)
        libz.so.6 => /lib/libz.so.6 (0x802562000)
        libkrb5.so.10 => /usr/lib/libkrb5.so.10 (0x802776000)
        libgssapi.so.10 => /usr/lib/libgssapi.so.10 (0x8029e7000)
        libgssapi_krb5.so.10 => /usr/lib/libgssapi_krb5.so.10 (0x802bf1000)
        libthr.so.3 => /lib/libthr.so.3 (0x802e0b000)
        libc.so.7 => /lib/libc.so.7 (0x80081b000)

I added "LDFLAGS=-L/usr/local/lib -L/usr/lib" in /etc/make.conf and rebuit all dependesies  packages for git, but this step didn't help me.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2015-06-19 19:31:24 UTC
I'm going to assume this is some part of devel/git and assign to garga on that basis.  To submitter: it helps when you specifically state category/portname in the Summary.
Comment 2 a.ulasov 2015-07-15 07:32:06 UTC
The issue has gone with the curl 7.43.0_1.