stefan k has asked for the wisdom of the Perl Monks concerning the following question:

Fellow Monks,
I am getting the errormessage in the title of this node (with the far too many explamation marks removed;-) when running a rather long perl script (which I did not write, and which does not use strict but that's another story and hopefully not connected to this error) on

The program does a lot of databse stuff and shows HTML pages . It does not use CGI however.

Can anyone point me anywhere for enlightenment, or -better yet- just provide it here. Because searching web and news for this error yields the same question every now and then but no answers.

Kind Regards Stefan K

Regards... stefan k
you begin bashing the string with a +42 regexp of confusion

Replies are listed 'Best First'.
Re: INTERNAL ERROR: PerlParse did not exit clean
by Corion (Patriarch) on Feb 24, 2005 at 08:00 UTC

    I fear that without any sample code to reproduce this problem, we will not able to help you - the soothsayers have spread their wisdom for the month, the ESP-reader was frozen by the snow and the bird watchers have no birds to watch.

    Copy your script to a different place, and verify that the error still occurs. Then start deleting lines, until the error stops occurring. Then slowly start adding lines back in, and try to keep the error away. Maybe brian's Guide to Solving Any Perl Problem can be of help. I would recommend you move away from IIS, to exclude the possibility of ActivePerl / PerlScript / ISAPI being the problem first. If that removes the problem, the problem likely is not with Perl, but with PerlScript / IIS / ISAPI.

[reply]
      Hi,
      of course we're are currently in the process of getting this thing to a linux box with apache. We'll see what will happen.

      The sad side of this is: the error is not reproducible. It occurred once during a nightly stress-test. We set up another server (w/o any other software) and that machine is running just fine. The first box also run some virus scanning software as well as backups. Rather complicated environment :-(

      I am not hoping for a code analysis here, just a pointer where the problem may be lurking.

      Regards... stefan k
      you begin bashing the string with a +42 regexp of confusion

[reply]

        Check line 418. I think the semicolon should be a comma.

        ???

        A vague question can only get a vague answer, if any at all. This is one of the ones that can't get any answer. If the question does not contain the problem (nor the error message, which this error message is completely unhelpful), then the problem cannot be solved. It's sorta like saying I have twelve pages of algebra which works out to x = 0, y = 0, when one of the equations is x = y + 1. And then asking where I made a mistake.

        I sympathise. I really do. But, as Corion implicated, we'd need to be mind-readers to get your problem.

[reply]
Re: INTERNAL ERROR: PerlParse did not exit clean
by stefan k (Curate) on Feb 28, 2005 at 13:38 UTC
    Fellow Monks,
    thanks for taking your time. I thought I had pointed out that I do not need help with a perl-code problem here. The answer I was hoping for and that I finally found myself was just, that this messages comes from the ISAPI module.

    I do not know what may have caused it but I know that I do not have to deal with any perl internals (and the error message suggested something in that direction) nor that the code is a total mess.

    Regards... stefan k
    you begin bashing the string with a +42 regexp of confusion

[reply]

Back to Seekers of Perl Wisdom