Most Esteemed Monks,

(By the way, I checked the debugging FAQ first.)

Anyway, I will bother saying a bit about myself (briefly). 47 years old. Made career switch from semiconductors to IT (six years ago). Laid off awhile back and generic skills from last job mainly perl and unix OS (read: REAL marketable - NOT!). My perl work was really scripting, but I did it for 5 years, as said.

I am trying to hone up my perl skills (I love this language) and make it as a developer.

Anyway, here is my question. There is a position out there with semiconductor application. It involves troubleshooting code that has 500,000 lines (reputably very well documented). Now, the code I wrote ranged from maybe 200 to 500 lines.

I am wondering about a hierarchy of debugging utilities/skills in descending order of significance that would assist in zeroing in on where problems might reside.

Or am I just peeing in the wind? (Too advanced for a scripter?)

Thanks In Advance,

o2

---

---

• 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.