[OpenBSD] staticperl dying unexpectedly with Coro/jit...

[nomad at null.net]

On Thu Oct 27, 2016 at 03:59:41PM +0200, nomad at null.net wrote:

> If I disable the JIT feature (also had to learn about the fact that
> Coro has a bunch of features) I no longer see the abort under
> staticperl.

So the above is true for the test case of "Coro::State->VERSION".
However now that I can build my staticperl-based application (with
CORO_JIT=n) I still see an abort at runtime:

    This GDB was configured as "amd64-unknown-openbsd6.0"...
    Core was generated by `bif'.
    Program terminated with signal 6, Aborted.
    Loaded symbols for /mark/src/bif/static/src/bif
    Reading symbols from /usr/lib/libm.so.9.0...done.
    Loaded symbols for /usr/lib/libm.so.9.0
    Reading symbols from /usr/lib/libc.so.88.0...done.
    Loaded symbols for /usr/lib/libc.so.88.0
    Reading symbols from /usr/libexec/ld.so...done.
    Loaded symbols for /usr/libexec/ld.so
    #0  0x00001b8dc91ac3ca in _thread_sys___syscall () at <stdin>:2
    2       <stdin>: No such file or directory.
            in <stdin>

    (gdb) backtrace
    #0  0x00001b8dc91ac3ca in _thread_sys___syscall () at <stdin>:2
    #1  0x00001b8dc91f810a in *_libc_mmap (addr=Variable "addr" is not available.
    )
        at /usr/src/lib/libc/sys/mmap.c:47
    #2  0x00001b8ba8b2a9e4 in coro_stack_alloc (stack=0x1b8dcea5f608, size=Variable "size" is not available.
    )
        at coro.c:749
    #3  0x00001b8ba8b2acde in cctx_new_run () at State.xs:1596
    #4  0x00001b8ba8b2c572 in transfer (prev=0x1b8e7e6d9d00, next=0x1b8e468b4700,
        force_cctx=Variable "force_cctx" is not available.
    ) at State.xs:1749
    #5  0x00001b8ba8b2c6d6 in pp_slf () at State.xs:2752
    #6  0x00001b8ba8bc9429 in Perl_runops_standard () at run.c:42
    #7  0x00001b8ba8b6c23e in perl_run (my_perl=Variable "my_perl" is not available.
    ) at perl.c:2460
    #8  0x00001b8ba8a4202d in main (argc=2, argv=0x7f7fffff2558) at bundle.c:15952
    Current language:  auto; currently asm

So perhaps not a Coro/JIT issue at all.

-- 
Mark Lawrence