Someone is calling _optimal_blksize("").
The fastest way I know to find this is to add -d to the Perl command line so the debugger runs then type "c" at the debugger prompt. This will cause you to get a stack backtrace when a warning happens, which is usually enough to track down the source of the bug.
I wish the debugger had an option to break on warnings. It would be easy to hack that option in by having dbwarn() check if the warnLevel option is greater than 1 and, if so, force $single= 1 when it is finished. I'll try to find time to send in a patch for that. (:
I suspect (and hope) that there is a module that provides stack backtraces for warnings via a simple
-Mmodule=option command-line switch to Perl, but I'm not aware of one.
(but my friends call me "Tye")
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||