in reply to what causes a segmentation violation

Your segmentation violation should produce a core file ('core' in the current working directory of the process). Use 'file core' to find out the name of the program which produced the core dump, probably perl in your case. Then use a debugger (gdb, dbx, etc.) giving that program name and the core file name as arguments. A stack backtrace via 'where' or similar should show you where the segmentation violation occurred, after that you're on your own. You may need to tweak some permssions and/or settings to get SIGSEGV to produce a core file. 'man core' for further details.
  • Comment on Re: what causes a segmentation violation