Re^2: Catching GD warning

Well actually no, I already tried that:

use strict;
use warnings;

use GD;

$SIG{__WARN__} = sub { print "Caught warning: ".$_[0] };

my $image;

eval {
    ($image = GD::Image->new("test.jpg")) or warn "Error: ".$!;
};

if ($@) {
    print "Caught ".$@;
}

if (defined($image)) {
    print "Image is defined: ".$image."\n";
}
[download]

produces:

Corrupt JPEG data: 104 extraneous bytes before marker 0xd9
Image is defined: GD::Image=SCALAR(0x817eba4)
[download]

What am I missing?

Comment on Re^2: Catching GD warning Select or Download Code

Replies are listed 'Best First'.
Re^3: Catching GD warning by wazoox (Prior) on May 03, 2006 at 15:19 UTC
~~Looks like a bug to me. If GD::Image is sending something to `STDERR` (like it seems to) then it should be manageable thru `$SIG{__WARN__}`~~. Try redirecting the STDERR and see what's happenning. Update: Looks like actually XS Module stderr can't be easily catched, there's even a module for that: IO::CaptureOutput, hence that should provide you with the solution to your problem.	[reply] [d/l] [select]