[magick-users] Segfault with PerlMagick 6.2.9-2, Perl 5.8.8 on
Linux 2.6.14
Neil Gunton
neil at nilspace.com
Tue Aug 29 18:57:15 CDT 2006
Neil Gunton wrote:
> Hi, I have been using ImageMagick successfully for years with pre-built
> packages (Perl and Magick) on both Slackware 10 and Debian Sarge AMD64.
>
> I am currently trying to track down an unrelated problem on my server,
> and as part of this process I am building my own Perl from source (first
> of all on my dev workstation). I'm running Slack 10.1, 2.6.14 custom
> kernel, and just built Perl 5.8.8 from source, likewise ImageMagick
> 6.2.9-2. All make tests run successfully on both packages.
>
> But when I try using ImageMagick from the new Perl on this setup, I get
> a segmentation fault on the Read statement. Here's a minimal case:
>
> #!/usr/bin/perl -w
> use strict;
> use Image::Magick;
> my $image = new Image::Magick;
> my $read_status = $image->Read('image.jpg');
>
> The Read statement is where is segfaults.
>
> I don't really have any idea why this would be happening. I tried
> reverting to my old Perl (5.6.1) and it then works ok. I built Perl
> mostly using the defaults (no threads, dynamic loading, no shared libs).
>
> The ImageMagick utilities seem to work - at least, 'display' does.
>
> Any ideas how I can track down what's going on here? Or is this more
> something that I need to ask over on the Perl group? Are there any
> 'tricks' I need to know about in the interaction between ImageMagick and
> Perl? I don't see why all the PerlMagick tests would work ok, but not my
> minimal program. This is what stumps me. Surely them succeeding would
> mean that the basic interaction between ImageMagick and Perl is working
> ok? How would they be any different from my minimal program?
>
> I also removed my old version of Perl, just to make sure there weren't
> any lib conflicts going on here.
>
> I also tried compiling Perl 5.6.2 just to see if this was a problem with
> later versions of perl, but the same exact thing happens.
>
> Any advice, pointers or suggestions on how to track down where the
> problem is would be much appreciated.
I discovered the problem - it was an old install of ImageMagick which
was via the Slack package system (I had assumed the only previous one
was compiled from source). So once I removed the old version, and
re-installed the new one, everything seems to work ok.
Sorry to bother everybody,
-Neil
More information about the Magick-users
mailing list