Will do.  For right now, I have a hunch that Crypt::SSLeay may *not*
be thread safe.  I'm using WWW::Mechanize on some SSL sites in a
multi-threaded fashion and I'm getting the following error
periodically:

*** glibc detected *** /usr/bin/perl: double free or corruption
(!prev): 0x0c061650 ***
======= Backtrace: =========
/lib/libc.so.6[0x4e5424]
/lib/libc.so.6[0x4e7206]
/lib/libc.so.6(__libc_realloc+0x101)[0x4e7d30]
/lib/libcrypto.so.5[0x6c1b95]
/lib/libcrypto.so.5(CRYPTO_realloc+0x81)[0x6c21e4]
/lib/libcrypto.so.5(sk_insert+0xce)[0x70c5f0]
/lib/libcrypto.so.5(sk_push+0x2a)[0x70c6fa]
/lib/libcrypto.so.5(EVP_PBE_alg_add+0x6e)[0x71958f]
/lib/libcrypto.so.5(PKCS12_PBE_add+0x3e)[0x74ffb2]
/lib/libcrypto.so.5(OpenSSL_add_all_ciphers+0x4ed)[0x717639]
/lib/libcrypto.so.5(OPENSSL_add_all_algorithms_noconf+0x17)[0x71713f]
/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi/auto/Crypt/SSLeay/SSLeay.so(XS_Crypt__SSLeay__CTX_new+0x33c)[0xecd990]
/usr/lib/perl5/5.8.6/i386-linux-thread-multi/CORE/libperl.so(Perl_pp_entersub+0x3a5)[0x39398c]
/usr/lib/perl5/5.8.6/i386-linux-thread-multi/CORE/libperl.so(Perl_runops_debug+0x141)[0x3756e1]
/usr/lib/perl5/5.8.6/i386-linux-thread-multi/CORE/libperl.so[0x322b9e]

[... snip ...]

A quick Google search resulted in a few hits with others having
similar problems.  It's certainly not definitive yet, but this is
where I'm going to focus my efforts.  If anyone is using Crypt::SSLeay
(through LWP or Mechanize) in a multi-threaded fashion successfully,
I'd be interested in hearing from you.  I'll let you know what I find.
 If anyone has any debugging tips for this type of error, I'd be happy
to try them out!  :-)

Chris

On 4/17/06, Andy Lester <[EMAIL PROTECTED]> wrote:
>
> On Apr 17, 2006, at 4:36 PM, Christopher Hart wrote:
>
> > Can anyone speak to the thread-safeness of WWW::Mechanize?  Is anyone
> > out there using it in a multi-threaded program?
>
> Whatever you find out, please write up something that I can put into
> the FAQ.
>
> Thanks,
> Andy
>
> --
> Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
>
>
>
>

Reply via email to