Coro segfault

[Marc Lehmann]

On Fri, Mar 21, 2014 at 05:15:44PM +0400, Andrey Sagulin <say42 at ya.ru> wrote:
> >>C-hacker so I cannot provide more details.
> >the "bt" command gives a backtrace, which is important to have.

Right, I forgot you also need the debugging info for the Coro module,
however, this backtrace already tells us that the crash happens when the
semaphore is up'ed, and that means almost certainly it is the perl bug
where a destructor is called but the object has already been freed.

As mentioned before, the easiest workaround is to exit with POSIX::_exit
or equivalent. Trying to work around it is possible (by making sure all
relevant destructors are called before exiting, for example, by letting
the async run to it's end, or cancel'ing it), but usually very hard.

> debugperl crash with a very long error message:

debugperl in ubuntu is probably the same thing as in debian - perl compiled
with debug checks. these checks are quite unreliable, and not really
compatible with code compiled without them, so this is almost certainly
harmless and unrelated.

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