Comments on: Finding the cause of inexplicable warnings in XS code http://blog.timbunce.org/2008/05/08/finding-the-cause-of-inexplicable-warnings-in-xs-code/ Listen. Reflect. Explore. Solve. Tue, 10 Jan 2012 18:35:08 +0000 hourly 1 http://wordpress.com/ By: Shawn M Moore http://blog.timbunce.org/2008/05/08/finding-the-cause-of-inexplicable-warnings-in-xs-code/#comment-1080 Wed, 12 Aug 2009 18:21:01 +0000 http://timbunce.wordpress.com/?p=39#comment-1080 Just to be a little friendlier to your users, I would gracefully overriding $SIG{__WARN__} instead of blindly overwriting it:

    my $old_warn = $SIG{__WARN__} || sub { warn @_ };
    local $SIG{__WARN__} = sub {
        CORE::dump if $_[0] =~ /uninitialized value in subroutine entry/;
        $old_warn->(@_);
    };

Handy trick though!

]]> By: Perl Coding School » Blog Archive » perl code [2008-05-08 11:12:01] http://blog.timbunce.org/2008/05/08/finding-the-cause-of-inexplicable-warnings-in-xs-code/#comment-170 Thu, 08 May 2008 11:21:55 +0000 http://timbunce.wordpress.com/?p=39#comment-170 [...] Finding the cause of inexplicable warnings in XS code By TimBunce Perl is reporting the last line of perl code that was executed at the same or higher level in the stack. So other perl code, such as a callback, may have been executed between entering xsub() and the warning being generated, … Not this… – http://blog.timbunce.org [...]

]]>