Duncan Garland wrote:
Has anybody had any thoughts about this problem?
Looking at the number of answers to your problem, I'm tempted to answer
"No".
Signal SEGV at /usr/lib/perl5/Net/SSL.pm line 131
SEGV is usually a pointer running amok, or a hardware problem (CPU
running too hot, memory chip broken, bus problems)
The script isn't new, it's been running for years. The problem has
occurred because we are upgrading to Debian Lenny and Perl 5.10.
"Never change a running system"
Are you mixing parts of the old and the new system, i.e. Perl XS modules
compiled against an older Debian version now running on the new one?
Alexander
--
Alexander Foken
mailto:alexan...@foken.de http://www.foken.de/alexander/
