Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re^4: Storable core dumping...

by devnul (Monk)
on Jun 30, 2004 at 00:19 UTC ( #370654=note: print w/replies, xml ) Need Help??

in reply to Re^3: Storable core dumping...
in thread Storable core dumping...

Just a few comments:

I don't think that $path/$name is corrupt because it would never get into this code area if there were a problem with either $path or $name (I.E. $path has to be a directory which is writable and $name has to be a valid filename).

As I may have forgotten to mention: this is not a reproducable bug.. It happens very rarely and I've been unsuccessful in creating some snippet which would reproduce it...

As for the "umm, yeah, whatever" comment: Some of us aren't avid C programmers and we do the best we can with what we know. If there is something else that I could do or some piece of information I could provide please let me know, but please if you are going to dis my attempt at least tell me why you are doing so. Is it so useless to look at changes between versions to try and find some evidence that your bug was resolved?

Also, is it at all noteworthy that this is happening in perl_destruct, or is that rather inconsequential to the issue?...

I will certainly send this on to the Perl folks, at any rate, if no resolution can be found here.... For some reason I get a queasy feeling about upgrading Storable... I'd at least like to be able to point at some code that changed which is likely to have solved this problem before doing it.....

- Greg

Replies are listed 'Best First'.
Re^5: Storable core dumping...
by PodMaster (Abbot) on Jun 30, 2004 at 00:33 UTC
    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.

    PS - 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.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://370654]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (2)
As of 2023-09-22 20:53 GMT
Find Nodes?
    Voting Booth?

    No recent polls found