SegFault in AnyEvent::Fork::Pool

[Marc Lehmann]

On Sat, Oct 25, 2014 at 01:08:07PM -0400, Robert Schmidt <rjeschmi at gmail.com> wrote:
> Using the on_destroy callback to trigger the exit condition variable is a
> pretty clean. Unfortunately it seems to segfault on 5.20.1

Hmm, not good - either a bug in ::Pool or in Array::Heap. The good news
is, your testcase reproduces it, so it will be easy to fix.

> here is the backtrace from the core, ideas or suggestions on what other
> info I should provide are appreciated.
> 
> my test code is here: https://github.com/rjeschmi/AnyEvent-Fork-Pool-Test

The testcase is perfect, thanks :)

Some unrelated (to the bug) comments:

a) the next version of AnyEvent::Fork::Pool will _not_ autoload
   AnyEvent::Fork anymore (the reason was that it had a dependency on
   that module anyway, but this has changed, as you can also use
   AnyEvent::Fork::Remote).

b) You *could* just move MyWorker.pm to the toplevel dir and save the "use
   lib" if you wanted. That doesn't make it any better, just pointing
   out an alternative :)

-- 
                The choice of a       Deliantra, the free code+content MORPG
      -----==-     _GNU_              http://www.deliantra.net
      ----==-- _       generation
      ---==---(_)__  __ ____  __      Marc Lehmann
      --==---/ / _ \/ // /\ \/ /      schmorp at schmorp.de
      -=====/_/_//_/\_,_/ /_/\_\