in reply to Re: forking memory problem
in thread forking memory problem

You should always turn on use strict; in your code, especially when your code is quite complex.

You mean, modern Perl will segfault (because that's what the error message seems to indicate) if you don't turn on strict? Where is that documented?

Abigail

Replies are listed 'Best First'.
Re: Re: forking memory problem
by Roger (Parson) on Nov 28, 2003 at 10:28 UTC
    That was just a general comment I made about the coding style, not to do with the segfault.

      Well, it turns out that running it on Perl 5.8 - it works.
      Perl 5.6 was a little flaky with the memory issue.