No really. The error you got is a memory protection fault.
That means that somewhere in perl the executable or in the
modules added to perl that tie to it on a .so or .dll basis
are making a mistake. Generally it is trying to access a
variable that has already been destroyed by perl or stepping
outside of a memory boundary set up by a string. As tye
points out, signals can wind up trying to deal with bad
data because they can catch perl in between critical steps
in certain circumstances and leave things half finished.
Based on the error having two locations that are the
same I'd bet on the interpreter having it's instruction pointer
sent out to never-never land and trying to execute a portion
of blank memory.
If you don't at least try no one will ever be able to
help you with this problem. Really. I'm not kidding, the
error you listed is among the most generic errors in the
entire computer world. All it tells us is that something
somewhere tried to do something in a place where it wasn't
allowed.
Your line "perhaps someone else came across the same problem and
resolved it somehow" might be re-written "perhaps someone else
came across a rock and remembers it." There are too many
rocks you have to at least tell us what road you are on
and which way you were looking.
--
$you = new YOU;
honk() if $you->love(perl) | 