No such thing as a small change | |
PerlMonks |
Re^2: Techniques for isolating bugs in perlby Ytrew (Pilgrim) |
on Oct 21, 2004 at 19:44 UTC ( [id://401289]=note: print w/replies, xml ) | Need Help?? |
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
In Section
Seekers of Perl Wisdom
|
|