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
Date: Friday, May 11, 2018 at 6:22 AM
To: Rich Salz , openssl-users
Subject: Re:
Hi Rich,
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==
The print routine does not free anything.
From: Raghavendra a
Reply-To: openssl-users
Date: Friday, May 11, 2018 at 5:53 AM
To: openssl-users
Subject: [openssl-users] freeing of X509_CRL object
Hi All,
In my program,
Hi All,
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: