Re^2: Debugging forking perl script? GDB?

No fork bomb. Just sometimes one of the children decides to loop forever somewhere...

perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'

Comment on Re^2: Debugging forking perl script? GDB? Download Code

Replies are listed 'Best First'.
Re^3: Debugging forking perl script? GDB? by Anonymous Monk on Nov 21, 2019 at 08:36 UTC
Include the PID and workload information (request url, rpc method name, queue item details, etc) in your logs along with start/end timestamps for processing the work. You can then look up the PID in the logs and find out what that pesky pegged worker is up to.	[reply]