Something else is going wrong. Is that the only valgrind error? Are you sure you didn’t free the object in your code?
From: Raghavendra a <raghuasit@xxxxxxxxx>
Date: Friday, May 11, 2018 at 6:22 AM
To: Rich Salz <rsalz@xxxxxxxxxx>, openssl-users <openssl-users@xxxxxxxxxxx>
Subject: Re: freeing of X509_CRL object
Thanks for information.
Any idea, why is X509_CRL_free reporting below error with valgrind?
Valgrind output:
==31919== Invalid read of size 4
==31919== at 0xB475EF2: CRYPTO_atomic_add (threads_pthread.c:155)
==31919== by 0xB355537: asn1_do_lock (tasn_utl.c:79)
==31919== by 0xB352767: asn1_item_embed_free (tasn_fre.c:88)
==31919== by 0xB3528D4: ASN1_item_free (tasn_fre.c:20)
Regards,
Raghavendra
On Fri, May 11, 2018 at 3:40 PM, Salz, Rich via openssl-users <openssl-users@xxxxxxxxxxx> wrote:
The print routine does not free anything.
From: Raghavendra a <raghuasit@xxxxxxxxx>
Reply-To: openssl-users <openssl-users@xxxxxxxxxxx>
Date: Friday, May 11, 2018 at 5:53 AM
To: openssl-users <openssl-users@xxxxxxxxxxx>
Subject: freeing of X509_CRL object
In my program,
converting X509_CRL object to string format using X509_CRL_print and BIO_get_mem_data. after that if de-allocate _x509crl using X509_CRL_free. it is crashing with below reason.
Valgrind output:
==31919== Invalid read of size 4
==31919== at 0xB475EF2: CRYPTO_atomic_add (threads_pthread.c:155)
==31919== by 0xB355537: asn1_do_lock (tasn_utl.c:79)
==31919== by 0xB352767: asn1_item_embed_free (tasn_fre.c:88)
==31919== by 0xB3528D4: ASN1_item_free (tasn_fre.c:20)not sure if X509_CRL_print de-allocates some part of _x509crl , external freeing of X509_CRL again leading to double free?
Please help on this issue.
Regards,
Raghavendra
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
