Re: Debugging DESTROY calls in forking application

If you are sharing data between threads perhaps there is a deadlock during DESTROY? that is, both a child and a parent try to destroy the same thing but each one thinks that the other is still using it? btw, if you use threads then those print statements will not be synchronised?

Comment on Re: Debugging DESTROY calls in forking application

Replies are listed 'Best First'.
Re^2: Debugging DESTROY calls in forking application by cavac (Prior) on Mar 13, 2020 at 08:49 UTC
It's a webserver backend. It doesn't call back to the main process. And it's forking, not threading. `perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'`	[reply] [d/l]
Re^3: Debugging DESTROY calls in forking application by bliako (Abbot) on Mar 13, 2020 at 10:13 UTC
Oh sorry, I missed the fork vs thread. So no shared data.	[reply]