in reply to Tracking down the source of a new 5.10 warning

You say your trick of $SIG{__WARN__} = ... isn't working. Perhaps the warning occurs prior to your assignment. Try executing that assignment very early, perhaps in a BEGIN block.

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

Replies are listed 'Best First'.
Re^2: Tracking down the source of a new 5.10 warning
by mpeters (Chaplain) on Sep 16, 2009 at 18:08 UTC
    Ok, I've tracked down the problem to Regexp::Common. I've changed places in the code that used to have:
    use Regexp::Common;
    to instead
    use Regexp::Common qw(number);
    Which should actually reduce memory usage as well. And the reason that my Carp/$SIG{__WARN__} trick didn't work was because this was a place in the test suite that generated code and executed it in another process (with a fresh new perl). Thanks for all the suggestions.

    -- More people are killed every year by pigs than by sharks, which shows you how good we are at evaluating risk. -- Bruce Schneier

      Ah. If you'd wanted to affect another perl, you could use the environment variable PERL5OPT. I've occasionally run with it set to things like -MCarp::Always to convert all my programs to use verbose warnings.1

      ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊