Setting breakpoints in other files - That's the way I do it. I have not heard of a better way. Just set a breakpoint at the point to step-in, step-in at that point and then set another break point when you're in the other file. There maybe another way but it hasn't been a big enough pain for me to look.
Taming the printing of @_ — You're in a perl interpreter so, p $_[3]->{foo} will work. I also will use Data::Dumper; p Dumper \@_ in the debugger. I set my terminal to scoll 5000 lines to scroll over the result.
Fumble fingers and stacktrace — I would setup another terminal window with a small script that runs the part of the regex you're interested in. You can w $data to get the current value being evaluated. Then test it in you other window.
One key history — The debugger will repeat the last command if you just hit return.
grep
| XP matters not. Look at me. Judge me by my XP, do you? |
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.