Re^2: Monitoring child threads

At the moment a crash of a child thread only leads to console message.
The minimum is that the program terminates - the maximum is a more complex handling depending on the terminating thread.
I would like to have a different handling for incoming threads than outgoing threads, but this is the second step.

Comment on Re^2: Monitoring child threads

Replies are listed 'Best First'.
Re^3: Monitoring child threads by BrowserUk (Patriarch) on Jan 24, 2008 at 17:51 UTC
The typical way of handling crashing code it to wrap it in a block eval: `sub thread { eval{ ## code } or ##handle error. }` [download] If you can trap the error, you can then pretty much do anything that you need to do. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Monitoring child threads
by BrowserUk (Patriarch) on Jan 24, 2008 at 17:51 UTC

The typical way of handling crashing code it to wrap it in a block eval:

sub thread {
    eval{
        ## code
   } or ##handle error.
}
[download]

If you can trap the error, you can then pretty much do anything that you need to do.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

[reply]
[d/l]