SEGV in t/spec/S17-procasync/no-runaway-file-limit.t

gistfile1.txt

  dogbert@dogbert-ubuntu:~/repos/rakudo$ MVM_JIT_DISABLE=1 ./perl6-valgrind-m -Ilib t/spec/S17-procasync/no-runaway-file-limit.t
================================================================================================
This is Rakudo Perl 6 running in valgrind, a tool for debugging and profiling programs.
Running a program in valgrind usually takes *a lot* more time than running it directly,
so please be patient.
Valgrind options can be added with MVM_VALGRIND_OPTS environment variable.

This Rakudo version is 2019.07.1.105.g.082.c.09.e.0.e built on MoarVM version 2019.07.1.66.g.654.a.136.d.1,
running on ubuntu (18.04.2.LTS.Bionic.Beaver) / linux (60.Ubuntu.SMP.Tue.Jul.2.18.22.20.UTC.2019)
------------------------------------------------------------------------------------------------
==218523== Memcheck, a memory error detector
==218523== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==218523== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==218523== Command: /home/dogbert/repos/rakudo/install/bin/moar --execname=/home/dogbert/repos/rakudo/perl6-valgrind-m --libpath=/home/dogbert/repos/rakudo --libpath=/home/dogbert/repos/rakudo/blib --libpath= --libpath=/home/dogbert/repos/rakudo/install/share/nqp/lib /home/dogbert/repos/rakudo/perl6.moarvm --nqp-lib=/home/dogbert/repos/rakudo/blib -Ilib t/spec/S17-procasync/no-runaway-file-limit.t
==218523== 
--218523-- WARNING: unhandled amd64-linux syscall: 332
--218523-- You may be able to write your own handler.
--218523-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--218523-- Nevertheless we consider this a bug.  Please report
--218523-- it at http://valgrind.org/support/bug_reports.html.
1..1
==218523== Invalid read of size 2
==218523==    at 0x5028324: MVM_interp_run (interp.c:328)
==218523==    by 0x51E02F8: MVM_vm_run_file (moar.c:445)
==218523==    by 0x109819: main (main.c:302)
==218523==  Address 0x966de6c is 12 bytes after a block of size 2,048 alloc'd
==218523==    at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==218523==    by 0x5086E30: MVM_malloc (alloc.h:2)
==218523==    by 0x508740D: add_page (fixedsizealloc.c:110)
==218523==    by 0x508756E: alloc_slow_path (fixedsizealloc.c:133)
==218523==    by 0x50876D2: alloc_from_global (fixedsizealloc.c:174)
==218523==    by 0x5087766: MVM_fixed_size_alloc (fixedsizealloc.c:192)
==218523==    by 0x50877A1: MVM_fixed_size_alloc_zeroed (fixedsizealloc.c:201)
==218523==    by 0x5062EB8: allocate_frame (frame.c:299)
==218523==    by 0x5063B40: MVM_frame_invoke (frame.c:534)
==218523==    by 0x50E82CA: invoke_handler (MVMCode.c:10)
==218523==    by 0x502E384: MVM_interp_run (interp.c:1048)
==218523==    by 0x51E02F8: MVM_vm_run_file (moar.c:445)
==218523== 
==218523== Invalid read of size 2
==218523==    at 0x5026FCD: MVM_interp_run (interp.c:168)
==218523==    by 0x51E02F8: MVM_vm_run_file (moar.c:445)
==218523==    by 0x109819: main (main.c:302)
==218523==  Address 0x966de6e is 14 bytes after a block of size 2,048 alloc'd
==218523==    at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==218523==    by 0x5086E30: MVM_malloc (alloc.h:2)
==218523==    by 0x508740D: add_page (fixedsizealloc.c:110)
==218523==    by 0x508756E: alloc_slow_path (fixedsizealloc.c:133)
==218523==    by 0x50876D2: alloc_from_global (fixedsizealloc.c:174)
==218523==    by 0x5087766: MVM_fixed_size_alloc (fixedsizealloc.c:192)
==218523==    by 0x50877A1: MVM_fixed_size_alloc_zeroed (fixedsizealloc.c:201)
==218523==    by 0x5062EB8: allocate_frame (frame.c:299)
==218523==    by 0x5063B40: MVM_frame_invoke (frame.c:534)
==218523==    by 0x50E82CA: invoke_handler (MVMCode.c:10)
==218523==    by 0x502E384: MVM_interp_run (interp.c:1048)
==218523==    by 0x51E02F8: MVM_vm_run_file (moar.c:445)
==218523== 
==218523== Jump to the invalid address stated on the next line
==218523==    at 0x10: ???
==218523==    by 0x51E02F8: MVM_vm_run_file (moar.c:445)
==218523==    by 0x109819: main (main.c:302)
==218523==  Address 0x10 is not stack'd, malloc'd or (recently) free'd
==218523== 
==218523== 
==218523== Process terminating with default action of signal 11 (SIGSEGV)
==218523==  Bad permissions for mapped region at address 0x10
==218523==    at 0x10: ???
==218523==    by 0x51E02F8: MVM_vm_run_file (moar.c:445)
==218523==    by 0x109819: main (main.c:302)
==218523== 
==218523== HEAP SUMMARY:
==218523==     in use at exit: 99,353,193 bytes in 240,458 blocks
==218523==   total heap usage: 895,820 allocs, 655,362 frees, 698,329,197 bytes allocated
==218523== 
==218523== LEAK SUMMARY:
==218523==    definitely lost: 32 bytes in 1 blocks
==218523==    indirectly lost: 0 bytes in 0 blocks
==218523==      possibly lost: 448,000 bytes in 7,980 blocks
==218523==    still reachable: 98,905,161 bytes in 232,477 blocks
==218523==         suppressed: 0 bytes in 0 blocks
==218523== Rerun with --leak-check=full to see details of leaked memory
==218523== 
==218523== For counts of detected and suppressed errors, rerun with: -v
==218523== ERROR SUMMARY: 8 errors from 3 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)