Re: Odd eval Problem

It's hard to say what goes wrong. You talk about 20k lines of code being evalled, but you only show a few. There are known problems with eval, which especially arise if there are so called "failed" evals (that don't compile) and you have many evals. The causes are not well understood, but a failed eval could set perl into such a state that hundreds, if not thousands, of evals later there will be failures, including core dumps, infite loops, and possible other problems.

While evalling 20k lines should of course work, are you really sure you need to eval that much? It smells very fishy.

-- Abigail

Comment on Re: Odd eval Problem

Replies are listed 'Best First'.
Re: Re: Odd eval Problem by nontrivial (Novice) on Jun 11, 2001 at 05:46 UTC
Abigail, I only included the code I was having trouble with. :-) As I said in another reply, if all the code is in a text file it works fine. If I randomly move subroutines from the text file to the database, it seems, after pulling out about 20k of code eval seems to break. It boggles my neophyte Perl skills. I will explain in another reply why I need that many evals. James	[reply]
(Vynce) Re3: Odd eval Problem by Vynce (Friar) on Jun 11, 2001 at 06:34 UTC
is it possible that the database is not actually storing the whole pile of code? most databases have a size limit for each individual field. try retrieving it from the database and printing it to a file, then compare the new, DB-filtered file to your original file using diff. see if they are really still the same. that's my first guess, anyway.	[reply]