get the best and fastest answer
|
|
|
|
Clear questions and runnable code get the best and fastest answer |
|
| PerlMonks |
Re^4: Debugging DESTROY calls in forking applicationby cavac (Parson) |
| on Mar 10, 2020 at 14:42 UTC ( [id://11114075]=note: print w/replies, xml ) | Need Help?? |
|
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";'
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||||||