Re^16: does threads (still) memleak?

Hi, Looks great - thanks a lot (sorry for the late feedback). I do have a small problem though: when using this as-is, SIGINT gets ignored by the script. I can get around this using an endless loop in main before the joining:

while (!$stop) {
  sleep 1;
}

$sender->join;
[download]

Comment on Re^16: does threads (still) memleak? Download Code

Replies are listed 'Best First'.
Re^17: does threads (still) memleak? by BrowserUk (Patriarch) on Jan 14, 2009 at 17:16 UTC
Good catch. I often have `PERL_SIGNALS=unsafe` to avoid such problems. You might also consider Perl::Unsafe::Signals. 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^17: does threads (still) memleak?
by BrowserUk (Patriarch) on Jan 14, 2009 at 17:16 UTC

Good catch. I often have PERL_SIGNALS=unsafe to avoid such problems. You might also consider Perl::Unsafe::Signals.

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]