Skip to content

Instantly share code, notes, and snippets.

@MasterDuke17
Created August 7, 2018 23:26
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save MasterDuke17/563b6d65baf1474767148bb62adfaac4 to your computer and use it in GitHub Desktop.
Save MasterDuke17/563b6d65baf1474767148bb62adfaac4 to your computer and use it in GitHub Desktop.
perl6-valgrind-m -e 'run("curl", :enc<utf8-c8>, :out, "-s", "https://www.google.com").out.slurp.chars.say'
================================================================================================
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.349.g.81.a.5.e.4.ba.8 built on MoarVM version 2018.06.385.g.3.e.679.da.29,
running on arch (4.17.11.arch.1) / linux (4.17.11.arch.1)
------------------------------------------------------------------------------------------------
==22097== Memcheck, a memory error detector
==22097== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==22097== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==22097== Command: /home/dan/Source/perl6/install/bin/moar --execname=../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 -e run("curl",\ :enc\<utf8-c8\>,\ :out,\ "-s",\ "https://www.google.com").out.slurp.chars.say
==22097==
valgrind: the 'impossible' happened:
Unsupported arch_prctl option
host stacktrace:
==22097== at 0x580441BA: show_sched_status_wrk (m_libcassert.c:355)
==22097== by 0x580442D4: report_and_quit (m_libcassert.c:426)
==22097== by 0x58044517: panic (m_libcassert.c:502)
==22097== by 0x58044517: vgPlain_core_panic_at (m_libcassert.c:507)
==22097== by 0x5804454A: vgPlain_core_panic (m_libcassert.c:512)
==22097== by 0x580DAE22: vgSysWrap_amd64_linux_sys_arch_prctl_before (syswrap-amd64-linux.c:286)
==22097== by 0x580A0C23: vgPlain_client_syscall (syswrap-main.c:1857)
==22097== by 0x5809D48A: handle_syscall (scheduler.c:1126)
==22097== by 0x5809EBB6: vgPlain_scheduler (scheduler.c:1443)
==22097== by 0x580AED50: thread_wrapper (syswrap-linux.c:103)
==22097== by 0x580AED50: run_a_thread_NORETURN (syswrap-linux.c:156)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 22097)
==22097== at 0x401A1C5: ??? (in /usr/lib/ld-2.28.so)
==22097== by 0xBFEBFBFE: ???
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment