valgrind.log

dan@hermes:~/p6/modules$ pv6 -I perl6-gumbo/lib/ -I exemel/lib/ -I ./perl6-all-modules/cpan/MOZNION/HTML-Escape/lib/ ../blargh.p6
================================================================================================
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 2018.06.424.g.3.c.93.f.3.fae built on MoarVM version 2018.06.416.g.62.a.99.bcf.4,
running on ubuntu (18.04.1.LTS.Bionic.Beaver) / linux (4.15.0.29.generic)
------------------------------------------------------------------------------------------------
==31403== Memcheck, a memory error detector
==31403== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==31403== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==31403== Command: /home/dan/Source/perl6/install/bin/moar --execname=/home/dan/Source/perl6/install/bin/perl6-valgrind-m --libpath=/home/dan/Source/perl6/install/share/nqp/lib --libpath=/home/dan/Source/perl6/install/share/perl6/lib --libpath=/home/dan/Source/perl6/install/share/perl6/runtime /home/dan/Source/perl6/install/share/perl6/runtime/perl6.moarvm -I perl6-gumbo/lib/ -I exemel/lib/ -I ./perl6-all-modules/cpan/MOZNION/HTML-Escape/lib/ ../blargh.p6
==31403== 
==31403== 
==31403== Process terminating with default action of signal 11 (SIGSEGV)
==31403==  General Protection Fault
==31403==    at 0x507F9F0: unmanaged_size (NFA.c:314)
==31403==    by 0x5052490: process_worklist (collect.c:300)
==31403==    by 0x50527E1: MVM_gc_collect (collect.c:134)
==31403==    by 0x504DE50: run_gc (orchestrate.c:408)
==31403==    by 0x504EBA2: MVM_gc_enter_from_allocator (orchestrate.c:525)
==31403==    by 0x504F0B5: MVM_gc_allocate_nursery (allocation.c:32)
==31403==    by 0x504F33D: MVM_gc_allocate_frame (allocation.c:99)
==31403==    by 0x5028807: MVM_frame_move_to_heap (frame.c:631)
==31403==    by 0x502A362: MVM_frame_force_to_heap (frame.h:208)
==31403==    by 0x502A362: MVM_frame_capturelex (frame.c:1139)
==31403==    by 0x501D137: MVM_interp_run (interp.c:1179)
==31403==    by 0x5031EB5: start_thread (threads.c:87)
==31403==    by 0x5FBC6DA: start_thread (pthread_create.c:463)
==31403== 
==31403== HEAP SUMMARY:
==31403==     in use at exit: 72,489,784 bytes in 231,830 blocks
==31403==   total heap usage: 619,753 allocs, 237,986 frees, 291,063,639 bytes allocated
==31403== 

Memcheck: mc_main.c:5837 (vgMemCheck_is_valid_aligned_word): Assertion 'VG_IS_WORD_ALIGNED(a)' failed.

host stacktrace:
==31403==    at 0x580441BA: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)

sched status:
  running_tid=3


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.