Re: Read the blog post about highlights in OTP 24.0

Max Lapshin <[email protected]>
Newsgroups gmane.comp.lang.erlang.general
Message-ID <CAMxVRxA64h9KbUgpyw1XXL3nw3s2_GiV6qRDxtic88fiLFTzVw@mail.gmail.com>
Right now we have some crashes with our endless video-related nifs in flussonic.

Trying to prepare a minimal reproducible crash.

I don't know if this crashdump can help right now:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000556e8e61b322 in mbc_alloc_finalize (allctr=0x556e8f610340,
blk=0x7f1b85516700, org_blk_sz=139756177041040, flags=2, crr=0x2,
want_blk_sz=40,
    valid_blk_info=1) at beam/erl_alloc_util.c:2458
2458    beam/erl_alloc_util.c: No such file or directory.
[Current thread is 1 (Thread 0x7f1b805ba640 (LWP 3151586))]
(gdb) bt
#0  0x0000556e8e61b322 in mbc_alloc_finalize (allctr=0x556e8f610340,
blk=0x7f1b85516700, org_blk_sz=139756177041040, flags=2, crr=0x2,
want_blk_sz=40,
    valid_blk_info=1) at beam/erl_alloc_util.c:2458
#1  0x0000556e8e61b6a1 in mbc_alloc (allctr=0x556e8f610340, size=16)
at beam/erl_alloc_util.c:2530
#2  0x0000556e8e625de2 in do_erts_alcu_alloc (type=2402,
allctr=0x556e8f610340, size=16) at beam/erl_alloc_util.c:5989
#3  0x0000556e8e625fb5 in erts_alcu_alloc_thr_spec (type=2402,
extra=0x556e8e9d4230 <erts_allctr_thr_spec+48>, size=16) at
beam/erl_alloc_util.c:6063
#4  0x0000556e8e79ac0f in erts_alloc (type=2402, size=16) at
beam/erl_alloc.h:251
#5  0x0000556e8e79c69f in build_exec_return (p=0x7f1b52d93f40, rc=1,
restartp=0x7f1b805b5b00, orig_subject=139753942872354) at
beam/erl_bif_re.c:691
#6  0x0000556e8e79f98f in re_run (p=0x7f1b52d93f40,
arg1=139753942872354, arg2=139753942872458, arg3=139753942872729,
first=0)
    at beam/erl_bif_re.c:1404
#7  0x0000556e8e79fa4c in re_internal_run_4 (A__p=0x7f1b52d93f40,
BIF__ARGS=0x7f1b805b5c80, A__I=0x7f1b832e5ab8) at
beam/erl_bif_re.c:1421
#8  0x00007f1b82fc7371 in ?? ()
#9  0x0000000000000000 in ?? ()
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.