Re: segfault on writing an image?

I'm with BrowserUK .. that use of "$self->param('DBH')->prepare" strikes me as extremely fishy. But i can't be sure that anything weird is going on there, since you didn't include your whole CGI (where is $self initialized? what does "$self->param('DBH')" return? is it a real DBI database handle, or something of your own creation? .. we aren't mind readers you know.)

I also suspect that maybe the Segfault you see in your cron may not be the same problem as what you see in your CGI .. since the libraries "resizeImg" seems to be returning fine. (However, it's hard to be sure about that either, since I'm not entirely clear on what the two have in common -- you say the method is in "MLSUtils.pm", but later you say your cron uses "the same ImageUtils lib" .. so i'm not sure what you mean)

Comment on Re: segfault on writing an image?

Replies are listed 'Best First'.
Re^2: segfault on writing an image? by geektron (Curate) on Jul 15, 2004 at 14:46 UTC
the ImageUtils lib is really named MLSUtils ... i think i found a fix, BTW. explicitly setting the `$large` var, which is the Image::Magick object, seems to fix it, since the pre-return warning print, but the post-return warning (in the caller) never does. i think that somehow the vars in MLSUtils going out of scope is kicking something ...	[reply] [d/l]