Re: forcing stack backtrace in the case of unhandled exception/Perl error

[Randy W. Sims]

On 4/26/2004 1:02 PM, David Garamond wrote:

I've [re]discovered the wonderful world of Carp. I've now peppered most 
of my scripts with 'use Carp qw(verbose);'.

However, whenever things go wrong (like my program calls an undefined 
subroutine, or I tried to modify a constant), my program dies without 
the stack backtrace. Any idea how I can get a backtrace?

$SIG{__WARN__} = sub {
  # verbose output
}
$SIG{__DIE__} = sub {
  # verbose output
}
perldoc perlvar



--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>