in reply to Debugging perl crash

The stuff you're seeing is most likely due to something earlier corrupting the state of the perl interpreter, which is going to be hard to track down. This will be either due to a bug in the perl core itself, or due to a bug in an XS-based module you are loading. If the latter, see if there's a newer release of that module; if the former, try using perl 5.20.0; in either case, the bug may have been found and fixed.

Dave.

Replies are listed 'Best First'.
Re^2: Debugging perl crash
by vsespb (Chaplain) on Jun 27, 2014 at 15:49 UTC
    Thanks.
    I prefer to try to find exact reason (and PoC code) for this bug and either find workaround or report it to FreeBSD team. Otherwise my software will be unusable (with stock perl) under whole family of FreeBSD 10+ and maybe other systems using llvm+perl 5.16(+?)
      I prefer to try to find exact reason
      In that case you're going to need to become an expert in the internals of perl and do a lot of C level debugging. I'd strongly recommend before you go that route, of trying to reduce your code to a managable size, and in particular, to eliminate as many external dependencies as possible. At that point you will either have eliminated all XS-based modules (so the bug is in perl), or will have found out which XS module has the bug. Trying with with newer versions of perl or the module will show whether the bug has been fixed (in which case you can bisect to see what patch fixed the issue), or if the bug is still present, will show you who to notify.

      Dave.