comment on

First, I'm going to echo the "break it up" answer. If you're supporting this thing, you need to know what it does. That probably involves breaking it into pieces that work together. Me, I'm a fan of modules.

A more immediate solution is the __END__ token. Stick it in the middle and see if everything works. If it does, then move it to 75%, otherwise move it to 25%. You'll very quickly determine about where the problem is.

Another thing - write tests. Lots and lots of tests.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: perl crashes parsing huge script - how to find a line that crashes it? by dragonchild
in thread perl crashes parsing huge script - how to find a line that crashes it? by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks