[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2014-08-26 Thread Rich Salz via RT
Cannot reproduce, too many other variables (gost engine, php) and no response from original requestor. Closing ticket. -- Rich Salz, OpenSSL dev team; rs...@openssl.org __ OpenSSL Project

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-06 Thread Rainer M. Canavan via RT
On Apr 1, 2010, at 17:44 , Stephen Henson via RT wrote: That is most peculiar. If an ENGINE isn't in use I wouldn't expect that to happen unless something somewhere is loading one. OK, next step is to see what ENGINE it is. Can you in the debugger print out the engine structure for

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-06 Thread Rainer M. Canavan via RT
On Apr 2, 2010, at 15:30 , Stephen Henson via RT wrote: This looks suspicious: #3 0x414a0787 in engine_pkey_asn1_meths_free (e=0x39) at tb_asnmth.c:165 165 EVP_PKEY_asn1_free(pkm); Not sure where the 0x39 is coming from. In frame#2: #2

[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-06 Thread Stephen Henson via RT
[rainer-open...@7val.com - Tue Apr 06 10:53:48 2010]: On Apr 2, 2010, at 15:30 , Stephen Henson via RT wrote: This looks suspicious: #3 0x414a0787 in engine_pkey_asn1_meths_free (e=0x39) at tb_asnmth.c:165 165EVP_PKEY_asn1_free(pkm);

[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-06 Thread Stephen Henson via RT
[rainer-open...@7val.com - Tue Apr 06 10:53:48 2010]: On Apr 2, 2010, at 15:30 , Stephen Henson via RT wrote: This looks suspicious: #3 0x414a0787 in engine_pkey_asn1_meths_free (e=0x39) at tb_asnmth.c:165 165EVP_PKEY_asn1_free(pkm);

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-06 Thread Rainer M. Canavan
On Apr 2, 2010, at 15:30 , Stephen Henson via RT wrote: This looks suspicious: #3 0x414a0787 in engine_pkey_asn1_meths_free (e=0x39) at tb_asnmth.c:165 165 EVP_PKEY_asn1_free(pkm); Not sure where the 0x39 is coming from. In frame#2: #2

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-02 Thread Rainer M. Canavan
On Apr 1, 2010, at 17:44 , Stephen Henson via RT wrote: That is most peculiar. If an ENGINE isn't in use I wouldn't expect that to happen unless something somewhere is loading one. OK, next step is to see what ENGINE it is. Can you in the debugger print out the engine structure for

[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-02 Thread Stephen Henson via RT
This looks suspicious: #3 0x414a0787 in engine_pkey_asn1_meths_free (e=0x39) at tb_asnmth.c:165 165 EVP_PKEY_asn1_free(pkm); Not sure where the 0x39 is coming from. In frame#2: #2 0x414e525a in EVP_PKEY_asn1_free (ameth=0x833fc70) at

[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Rainer M. Canavan via RT
I'm using an apache 2.2.15 with php-5.2.13 and curl-7.20.0. When using openssl-1.0.0, I get easy to reproduce Aborts in CRYPTO_free if I reload a page while it is still loading. The problem reproducably goes away when I replace openssl-1.0.0 with 0.9.8m (and recompile the whole stack). OSes are

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Rainer M. Canavan via RT
On Apr 1, 2010, at 12:26 , Stephen Henson via RT wrote: Well first question is... are you compiling against the 0.9.8 headers instead of the 1.0.0 ones? No. I've had those problems with builds from scratch, i.e. completely empty source and destination directories as well. I also don't have

[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Stephen Henson via RT
[rainer-open...@7val.com - Thu Apr 01 11:00:08 2010]: I'm using an apache 2.2.15 with php-5.2.13 and curl-7.20.0. When using openssl-1.0.0, I get easy to reproduce Aborts in CRYPTO_free if I reload a page while it is still loading. The problem reproducably goes away when I replace

[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Stephen Henson via RT
[rainer-open...@7val.com - Thu Apr 01 12:36:16 2010]: On Apr 1, 2010, at 12:26 , Stephen Henson via RT wrote: Well first question is... are you compiling against the 0.9.8 headers instead of the 1.0.0 ones? No. I've had those problems with builds from scratch, i.e. completely

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Rainer M. Canavan
On Apr 1, 2010, at 12:26 , Stephen Henson via RT wrote: Well first question is... are you compiling against the 0.9.8 headers instead of the 1.0.0 ones? No. I've had those problems with builds from scratch, i.e. completely empty source and destination directories as well. I also don't have

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Rainer M. Canavan via RT
On Apr 1, 2010, at 13:04 , Stephen Henson via RT wrote: OK, I'm trying to see where that ENGINE call comes from. Are you using an ENGINE to load a private key? This is just a normal vhost in apache. Apparently, it's sufficient to just point a browser to an http URL of a large object (I'm

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Rainer M. Canavan
On Apr 1, 2010, at 13:04 , Stephen Henson via RT wrote: OK, I'm trying to see where that ENGINE call comes from. Are you using an ENGINE to load a private key? This is just a normal vhost in apache. Apparently, it's sufficient to just point a browser to an http URL of a large object (I'm

[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Stephen Henson via RT
[rainer-open...@7val.com - Thu Apr 01 11:00:08 2010]: Under certain circumstances, this turns into segfaults: Program received signal SIGSEGV, Segmentation fault. 0x4108a6a5 in free () from /lib/libc.so.6 (gdb) bt #0 0x4108a6a5 in free () from /lib/libc.so.6 #1 0x4141e06e in

Re: [openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Rainer M. Canavan via RT
On Apr 1, 2010, at 17:44 , Stephen Henson via RT wrote: That is most peculiar. If an ENGINE isn't in use I wouldn't expect that to happen unless something somewhere is loading one. OK, next step is to see what ENGINE it is. Can you in the debugger print out the engine structure for

[openssl.org #2215] crash in openssl-1.0.0 glibc detected httpd: free(): invalid pointer in libcrypto.so.1.0.0(CRYPTO_free)

2010-04-01 Thread Stephen Henson via RT
[rainer-open...@7val.com - Thu Apr 01 19:18:51 2010]: On Apr 1, 2010, at 17:44 , Stephen Henson via RT wrote: That is most peculiar. If an ENGINE isn't in use I wouldn't expect that to happen unless something somewhere is loading one. OK, next step is to see what ENGINE it