Running gdb (or adb, the HP/UX version) on the core file just gives me a back trace with no real information, other than the fact that segmentation fault caused the error. I already knew that. :-(
We don't have Devel::Trace installed, but I suspect it would just make the bug go into hiding again: adding the "-s" flag makes the bug go away.
By running a shell script, I determined that the minimum name that the program needed to be named to trigger the bug was 16 characters long. The bug only manifests itself when run from a certain directory, as well. Perhaps something involving a minimum path size is affecting it.
Certain changes to whitespace don't make the bug go away; others do. Reducing the size of certain comments can trigger/hide the bug.
This bug is very confusing: changes to comments affect it, suggesting that there is a problem with how the code gets parsed, yet it runs until the end of the program before dumping core.
--Ytrew
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.