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

How does the debugger do it? Could you replicate that?

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

Replies are listed 'Best First'.
Re^2: Forcing stacktrace, alternative to Carp::Always
by LanX (Saint) on Sep 27, 2019 at 23:09 UTC
    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

      > 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