in reply to Re: Forcing stacktrace, alternative to Carp::Always
in thread Forcing stacktrace, alternative to Carp::Always

I suppose by installing SIG handlers too, with the same potential problems.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

  • Comment on Re^2: Forcing stacktrace, alternative to Carp::Always

Replies are listed 'Best First'.
Re^3: Forcing stacktrace, alternative to Carp::Always
by LanX (Saint) on Sep 28, 2019 at 15:34 UTC
    > I suppose by installing SIG handlers too, with the same potential problems.

    just verified it. From perl5db.pl

    $SIG{__WARN__} = \&DB::dbwarn;

    and DB::dbwarn() is internally using Carp::longmess()

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice