Catching GD warning

Marcello has asked for the wisdom of the Perl Monks concerning the following question:

Hi,

I'm having problems catching a certain GD warning when using a (partially) corrupt JPEG file.

use strict;
use warnings;

use GD;

my $image = GD::Image->new("test.jpg");
[download]

Running this script produces the following warning on the command-line:

Corrupt JPEG data: 104 extraneous bytes before marker 0xd9
[download]

How can I catch this error in Perl? $SIG{__WARN__} is not working here. I would like to catch this error so I can remove the extraneous bytes from the original JPEG file.

Thanks

Comment on Catching GD warning Select or Download Code

Replies are listed 'Best First'.
Re: Catching GD warning by eff_i_g (Curate) on May 03, 2006 at 13:50 UTC
Look at error trapping here: eval	[reply]
Re: Catching GD warning by ady (Deacon) on May 03, 2006 at 14:42 UTC
`use strict; use warnings; use GD; my $image; # $image = GD::Image->new($data) # If something goes wrong, this call will return undef. # so one could do : ($image = GD::Image->new("test.jpg")) or warn "Error: $!"; # or if (! ($image = GD::Image->new("test.jpg")) ) { print "my error handling\n"; } # eval trapping would work too...` [download]	[reply] [d/l]
Re^2: Catching GD warning by Marcello (Hermit) on May 03, 2006 at 14:59 UTC
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?	[reply] [d/l] [select]
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]