Thanks for the tip. No, I don't call CRYPTO_malloc_init. But I don't think it is necessary. I'm pretty sure that I'm not mixing compiler options. Also, if this was the case it was crashing all the time, right? SSL connections work fine with any client except this HP Insight Manager thing.
Of course I can give it a try and see what happens. Thanks a lot. On Thu, Oct 29, 2009 at 5:40 PM, <aerow...@gmail.com> wrote: > CRYPTO_malloc is an internally-used function, to allocate memory. In any > event, though, do you do an earlier CRYPTO_malloc_init? > > http://openssl.org/support/faq.html#PROG2 > > -Kyle H > > On Thu, Oct 29, 2009 at 11:23 AM, Josue Andrade Gomes > <josue.gomes.honey...@gmail.com> wrote: >> >> Hi, >> >> Shortly: HP Insight Manager (a management tool) crashes my server SSL >> application. >> Operating system: Windows 2003 Server >> OpenSSL version: 0.9.8k >> Post-mortem debugger points the crash ocurring in a call to >> CRYPTO_malloc() inside SSLv3_client_method() >> (wich is weird since I never call this function). >> >> Any idea? Have someone seen this already? >> >> regards, >> josue >> >> The packet that causes the crash: >> >> No. Time Source Destination Protocol >> Info >> 34446 117.798401 <removed> <removed> SSL Client Hello >> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
