Does anyone know how to convince the perl debugger to put a breakpoint on waitpid()?
The reason I ask is I've got a program that does a lot of parallel work with fork() and it manages its own children. Unfortunately a module it uses (VM::EC2) was just updated on my system with the most recent version and it seems to now be reaping my child processes for me. I suspect that its happening somewhere deep in the bowels of module dependencies and grepping the code wasn't helpful. I'm hoping to catch the culprit by breaking on waitpid() and taking a look at the stack.In reply to Breakpoint on waitpid()? by slagperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |