The typical way of handling crashing code it to wrap it in a block eval:
sub thread { eval{ ## code } or ##handle error. }
If you can trap the error, you can then pretty much do anything that you need to do.
In reply to Re^3: Monitoring child threads
by BrowserUk
in thread Monitoring child threads
by weismat
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |