Skip Menu |

This queue is for tickets about the Crypt-SSLeay CPAN distribution.

Report information
The Basics
Id: 67600
Status: new
Priority: 0/
Queue: Crypt-SSLeay

Owner: Nobody in particular
Requestors: scott_stone [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

Subject: Crypt::SSLEay causes SIGSEGV when used with perl threads
Date: Tue, 19 Apr 2011 19:25:49 -0700
To: <bug-Crypt-SSLeay [...]>
From: <scott_stone [...]>
Download (untitled) / with headers
text/plain 1.4k
I'm using the Frontier XMLRPC module with Perl 5.008 on CentOS 5.5. The Frontier module is connecting to a custom XMLRPC interface using HTTPS. Frontier can use either Crypt::SSLeay or IO::Socket::SSL. My code makes use of Perl threads. If the system has IO::Socket::SSL installed, it works as intended, 100% of the time. If I instead of Crypt::SSLeay installed, it fails with a SIGSEGV 100% of the time. If I run the code in a single thread, ie, disable all threading functions in my perl code, then it works fine with either module. This leads me to believe that Crypt::SSLeay has a problem with the Perl threads library (I'm using the built-in threading functions in PERL). I am running 0.57 of Crypt::SSLeay, from the RPMforge Extras distribution. If there is a way to recompile Crypt::SSLeay in such a way to make it "thread safe", please advise, as I can easily do that and repackage it for my purposes. Thanks in advance. ==================== Scott Stone <> Lead Developer, DCS-RD Trend Micro, Inc. TREND MICRO EMAIL NOTICE The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to