Skip Menu |
Report information
Id: 130645
Status: new
Priority: 0/
Queue: perl6

Owner: Nobody
Requestors: agentzh [at] gmail.com
Cc:
AdminCc:

Severity: (no value)
Tag: Bug
Platform: (no value)
Patch Status: (no value)
VM: (no value)



Date: Wed, 25 Jan 2017 16:15:10 -0800
To: rakudobug [...] perl.org
From: "Yichun Zhang (agentzh)" <agentzh [...] gmail.com>
Subject: [BUG] Entering an infinite hot loop during pre-compilation + RAKUDO_MODULE_DEBUG=1
Download (untitled) / with headers
text/plain 1.2k
Hello! I've noted that moar will enter an infinite hot loop when the RAKUDO_MODULE_DEBUG=1 environment is specified. The last few lines of the output on the terminal is like this: https://gist.github.com/agentzh/13bc32c6ed67c8dba8151c861903b0d1 Then it just hangs there. The moar process maxes out the CPU core: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10147 agentzh 20 0 140408 117760 24452 R 100.0 1.4 0:57.08 moar strace shows tons of the following write() syscall: write(2, " 1 10147 RMD: dependency checksum 7DE3572D8645BB1BB4E1928CE0EDFACC6CE644BD unit: 7DE3572D8645BB1BB4E1928CE0EDFACC6CE644BD\n", 124) = -1 EAGAIN (Resource temporarily unavailable) All identical. gdb shows the following backtrace: https://gist.github.com/agentzh/93fb82b1a4c61b4e2478f0b88e466d2e The version of my rakudo: $ perl6 --version This is Rakudo version 2017.01 built on MoarVM version 2017.01 implementing Perl 6.c. Details on my operating system: $ uname -a Linux fedora64 4.8.13-100.fc23.x86_64 #1 SMP Fri Dec 9 14:51:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Removing the RAKUDO_MODULE_DEBUG=1 environment makes the hot looping go away. Please let me know if you need any further information. Thanks! -agentzh


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org