Re: i2d_X509_CINF() crash/valgrind trace

2009-06-12 Thread Neil Youngman
On Friday 12 June 2009 02:12:06 Kyle Hamilton wrote: > This looks like you're trying to use a library compiled for > multithreading without providing it the address of a lock or unlock > function. > > This is, incidentally, programmer FAQ #1, readable at > http://openssl.org/support/faq.html#PROG1

Re: i2d_X509_CINF() crash/valgrind trace

2009-06-11 Thread Kyle Hamilton
This looks like you're trying to use a library compiled for multithreading without providing it the address of a lock or unlock function. This is, incidentally, programmer FAQ #1, readable at http://openssl.org/support/faq.html#PROG1 . -Kyle H On Thu, Jun 11, 2009 at 8:56 AM, Neil Youngman wrote

i2d_X509_CINF() crash/valgrind trace

2009-06-11 Thread Neil Youngman
I've got some crashes happening in i2d_X509_CINF(). I've manged to generate the valgrind trace below indicating where it's happening, but it's not yet obvious to me why it should happen. It's in some code that's been stable for ages (hence 0.9.6b) but there seems to be a rare situation in which