Hi Ynon. A few comments from the SSLeay documentation:
""" It is required to reset these callbacks to undef immediately after use to prevent memory leaks, thread safety problems and crashes on exit that can occur if different threads set different callbacks. """ So if LWP::Simple uses these callbacks, and then it is being Perl-level duplicated (on thread creation) and destroyed (on join), segfault is sure to come. So it is probably more of a bug for the LWP::Simple, but looking in the RT I see that nobody maintain this module. Shmuel. On 2011/01/15 18:28, ynon perek wrote: > Hi, > Thanks everyone for the comments. Will write to Florian see if he is > aware of the issue. > > Anyhow, I decided to put threading aside for now and put my money on > POE, hoping to get more stable code :) > > Cheers, > Ynon > > > On 14 January 2011 16:37, David Baird <[email protected] > <mailto:[email protected]>> wrote: > > Shmuel, > > > I took a look, and Net::SSLeay is an XS module, and completely not > > thread safe. > > (for example, it keeps hashs as global variables in the C code) > > Arigato for checking it out, it's what I suspected. > > David > _______________________________________________ > Perl mailing list > [email protected] <mailto:[email protected]> > http://mail.perl.org.il/mailman/listinfo/perl > > > > > _______________________________________________ > Perl mailing list > [email protected] > http://mail.perl.org.il/mailman/listinfo/perl _______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
