in reply to (tye)Re: eval + no warnings = no memory
in thread eval + no warnings = no memory

I reduced the program to the smallest size, but I can assure you that the behavior happens even if the eval statement is within a loop, or even within a procedure called by a loop (as this was the original case).

But it's a good guess though :)

Ciao,
Gryn

  • Comment on Re: (tye)Re: eval + no warnings = no memory

Replies are listed 'Best First'.
(tye)Re2: eval + no warnings = no memory
by tye (Sage) on Jan 30, 2001 at 12:04 UTC

    Ah, thanks for the info. From elsewhere in this thread, it sounds like the leak is in "stringy" eval for some versions of Perl on some platforms. I'm sure the porters would appreciate a bug report with the data collected so far. (:

            - tye (but my friends call me "Tye")
      One of the benefits of perlmonks is that I can turn to you all for this sort of information: Where do you report bugs?

      Ciao,
      Gryn

        The command "perlbug" should walk you through reporting a bug.

                - tye (but my friends call me "Tye")