I don't think that $path/$name is corrupt ...
$path/$name is your storable file, I'm saying maybe its contents are corrupt.
As for the "umm, yeah, whatever" comment: Some ...
I'm not an avid c programmer either, but that's besides the point. The last thing I want to do is touch C code, especially someone elses C code, especially since I might not have to. You're using an old perl with an old storable and you're having a segfault. You should try upgrading before you even think about debugging the C code in the background. s~umm, yeah, whatever~can't help you there~
Also, is it at all noteworthy that this is happening in perl_destruct, or is that rather inconsequential to the issue?...
Heh :) Did you try to upgrade (how about trying out those combinations I mentioned and see if something breaks -- you could even try upgrading perl)? Does it segfault before or after your program has done all it has to do? If its after, I say forget about it.
And then it's three AM and I'm on the corner, wearing my leather,
This dude comes up and he's, like, "Hey, punk", I'm, like, "Yeah, whatever".
|MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"|
|I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).|
|** The third rule of perl club is a statement of fact: pod is sexy.|