That's coming from within the libc open call. If you have debugging libc installed, running under gdb may help. Perl should not be able to do this to the system.1 What is your libc, OS and their patchlevels? One recent Linux release "featured" an fs corruption bug, so maybe booting a known good kernel is called for. A bad sector or corrupt inode could do this, so I think ehdonhon's suggestion of a fsck is a good idea at this point.
If you're not getting core dumps for gdb, you can try $SIG{SEGV} = sub{abort};. You will want the source of libc open() to know what names to look at.
The filesystem theory really doesn't fit crashing on the same file each time. I am puzzled..
1 Update: Overstated, withdrawn.
After Compline,
Zaxo
In reply to Re: Re: (2) Segmentation fault during file open
by Zaxo
in thread Segmentation fault during file open
by talexb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |