| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Alex Hunsaker <badalex(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
| Subject: | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |
| Date: | 2011-08-10 17:03:58 |
| Message-ID: | 5C19469D-B349-4627-BC49-F26352A741DA@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Aug 10, 2011, at 9:44 AM, Andrew Dunstan wrote:
> After some experimentation, I found that, at least on my system, if LWP uses Crypt::SSLeay for https requests then it sets an alarm handler, but if instead it uses IO::Socket::SSL an alarm handler is not set. So the answer to the OP's original problem is probably "make sure you have IO::Socket::SSL installed and that Crypt::SSLeay is not installed."
I think I'd also complain via bug-crypt-ssleay(at)rt(dot)cpan(dot)org that a library ought not to set signal handlers.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-08-10 17:27:18 | Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https |
| Previous Message | David E. Wheeler | 2011-08-10 17:01:43 | Re: Policy on pulling in code from other projects? |