Re^4: Debugging DESTROY calls in forking application

I tried it with -d:Trace, but all the extra stuff happening made timeouts happen which screwed up my tests.

But i agree, in many cases all that build in debugging/profiling/tracing functionality is a good way to find problems.

perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'

Comment on Re^4: Debugging DESTROY calls in forking application Download Code

Replies are listed 'Best First'.
Re^5: Debugging DESTROY calls in forking application by LanX (Cardinal) on Mar 10, 2020 at 15:30 UTC
CPAN has a big variety of modules in `Devel::` , like Devel::Trace , Devel::ebug , etc . I'd be surprised if it wasn't possible to limit the trace to DESTROY only. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply] [d/l]