> Somewhere, it uses $& or one of those operators that change the regex
engine of
> perl. I don't know if its been fixed in 5.8.7 or maint.
I'm running 5.8.7 and it still has this problem.
I'm currently working around it by not preloading Image::Magick and using
"require"
to load Image::Magick o
> I'm going to have to eat part/all of my words here as there is no port for
> p5-Image-Magick.
There is a port ImageMagick which also contains the perl module
Image::Magick.
I've mailed the maintainer. Not sure though if he would be able to fix it as
he might
not be into perl.
Kevin A. McGrail wrote:
If it helps, I am under the opinion that ImageMagick on a Linux box is
causing segfaults under modperl1 & 2 and I identified the issue years ago
but have just started tracking it back to ImageMagick. I expect to be
tackling this issue sometime very soon.
Ding!
Lightbulb
sage -
From: "Philip M. Gollucci" <[EMAIL PROTECTED]>
To: "Philip M. Gollucci" <[EMAIL PROTECTED]>
Cc: "Len Kranendonk" <[EMAIL PROTECTED]>;
Sent: Wednesday, November 09, 2005 12:02 PM
Subject: Re: Seg fault with Image::Magick on FreeBSD
Philip M. Gollucci wrote:
Len Kranendonk wrote:
As soon as I preload Image::Magick under mod_perl2 on FreeBSD (5.3,
5.4 and 6.0) I
get a "Segmentation fault (core dumped)" when I start Apache.
look in the Makefile for the Maintainer of the port.
if that doesn't work ports /at/ FreeBSD (dot)
Len Kranendonk wrote:
As soon as I preload Image::Magick under mod_perl2 on FreeBSD (5.3, 5.4
and 6.0) I
get a "Segmentation fault (core dumped)" when I start Apache.
look in the Makefile for the Maintainer of the port.
if that doesn't work ports /at/ FreeBSD (dot) org
or you can file a gnats
