on 4/16/02 10:40 AM, [EMAIL PROTECTED] purportedly said: > i have quite a heavy catalogger program, that uses DB_File BTrees for it's > indexes. The program ran very well till i upgraded to perl 5.6.1r1, but > macperl > itself was not very stable. The problem now is that occasionally the script > stops. > i don't know how to use the debugger, and learning will be my next step, if no > one can help. i've set the -w switch, am using strict, and sub END prints $! > and > $^E. neither is set when the program stops on it's own. it stops in the middle > of a specific subroutine, the one that does lexical parsing and cataloggin, at > it's very end, usually a bit before. > > i have reasons to believe that this is a memory problem, mainly because the > more > memory macperl has, the better this works, but there are no out of memory > complaints, or the panic msg.
If by "better this works" you mean that the script goes farther before stopping, it is possible there is a memory issue. I am surprised you aren't getting a panic, but IIRC, I think that will only appear if the macperl output window is open. I don't know if it is possible to trap a memory error in perl code, but if it can be done, perhaps that is happening. I.e., the error is being trapped and at some point a failure is being returned by a function where you may not be checking the return value, or simply returning on a general failure without complaint. If your index files are particularly large, you may need to try a different approach, like more smaller index files. Keary Suska Esoteritech, Inc. "Leveraging Open Source for a better Internet"
