In the first instance, under normal conditions, neither Perl nor an extension should coredump at all whatever you have in your own code; if it does then there is some basic problem with the build of Perl or the extension in question. That said it would appear that Data::Encrypted doesn't have any XS part: it hands off the actual encryption to some Crypt:: module which will almost certainly have some XS component (or use something that does like Math::Pari,) so this is where you are going to have to start looking for the cause of the coredump.
The easiest way to determine the point at which the coredump occurred is to point your debugger at it; for instance if you were using gdb you might have something like:
gdb --core ./core
of course you may have to determine what the actual command line is if you have a different debugger on your system.
A possible cause of a coredump could also be that some XS extension has been built with a different C compiler than that which was used to build the Perl: you can determine the compiler used (and the architecture the perl was built for) from the output of perl -V. If you have a prebuilt Perl that came with the OS it is often the case that this would be built with the vendors own compiler rather than, say, gcc (I don't know if this is the case with HP/UX) but it might be possible to get the packages you want prebuilt also.
/J\ |