Parrot 6.6.0 "Parrothead" | parrot.org/ | Log: irclog.perlgeek.de/parrot | #parrotsketch meeting Tuesday 19:30 UTC
Set by moderator on 23 July 2014.
01:45 FROGGS_ joined 01:51 Chirag joined
Chirag Coke: Hey! the build failure is on my Dev branch only (pcc-gh1083) 01:53
06:35 bighugedog joined 07:32 basiliscos joined 08:37 bighugedog joined 10:22 bighugedog joined 11:05 bighugedog joined 11:14 kid51 joined 12:15 atrodo joined
FROGGS rurban: when I see suh a thing in a bt for a perl6-p program: 12:37
Parrot_ext_call (interp=interp@entry=0x60f050, sub_pmc=0x35dce88, signature=signature@entry=0x7ffff7b2e18c "->") at src/extend.c:158
that looks like it is something about rakudo's ops, or maybe even nqp...
how can I find out what is called there? 12:38
the problem I try to hunt down is that we have something of type enum_class_Sub, which has PMC_data==NULL 12:40
the behaviour is identical on parrot 6.1.0, 6.4.0 and 6.6.0... now switching to HEAD... 12:41
the entire backtrace is here: gist.github.com/FROGGS/6a3d23f0b93db0a9938b 12:52
this issue causes more than 1600 spectest failures btw 12:53
my gut feeling tells me that this might be related: github.com/rakudo/rakudo/blob/nom/....ops#L1049 13:06
13:51 Chirag joined 14:47 rurban1 joined
rurban FROGGS: lemme check... 14:49
Parrot_ext_call is a normal method call (not vtable). The backtrace is not really helpful. Will try with a debugging build 14:50
nqp and rakudo HEAD? 14:54
Chirag rurban: Hey! I am getting a build failure with my branch - 15:10
too few positional arguments: 2 passed, 3 (or more) expected
rurban I'll check soon 15:11
Chirag ok
rurban first checking the perl6 problem
Chirag sure
rurban FROGGS: not repro. most spectests pass with nqp+rakudo HEAD and parrot 6.6.0 debugging. Messing with PERL6LIB? 15:57
Chirag: can repro $ ./miniparrot -Iruntime/parrot/include config_lib.pir 16:02
too few positional arguments: 2 passed, 3 (or more) expected
This is in the very first call to fill_params 16:05
with the sig PiSSoIpSnSoIpSnPoIp (Parrot_IMCCompiler_nci_compile_file) 16:08
FROGGS rurban: yes, nqp and rakudo HEAD will do
no, PERL6LIB is not set here 16:09
it also fails on other boxes
rurban interesting
FROGGS like Coke++'s smoke box: github.com/coke/perl6-roast-data/b...ummary.out 16:10
Coke I don't have the specific failure modes, only that the tests abort there. 16:14
i can get the specific failure modes, though. FROGGS - did you try reverting the rakudo commit I Id'd in my ticket? 16:15
(we still shouldn't be segfaulting, but that might help narrow down what the issue is)
rt.perl.org/Ticket/Display.html?id=122436 - the one example I bothered to pull from the spectests segfaults there. 16:16
FROGGS Coke: no, I've not tried that 16:17
Coke: will do that now
Coke just posted the segfault again in #perl6; thanks for helping track this down. 16:18
FROGGS Coke: reverting it helps 16:25
this is how it looks like when I invoke it several times: gist.github.com/FROGGS/5a8688b59c1b06137ec1 16:38
(using Test.pm instead of Test.pm.pir) 16:39
I'll strip down Test.pm now until it goes away
Chirag rurban: just went through that code but we never modified it.. (after the last task) 16:47
FROGGS rurban: hmmm, using a module triggers it (in combination with 'say :10("111")'), the module can be empty though 16:49
Chirag rurban: I suspect some problem with Parrot_CallContext_class_init 17:25
oops.. looks like you have your hands full :) .. will wait 17:26
Coke jnthn was also seeing a build failure ( I think ) on nqp-parrot on windows, which made it difficult for him to get near the segfault FROGGS is looking at; not sure if at a ticket was opened. I don't have a handy windows box to test. 17:51
FROGGS rurban: here is also now valgrind's output of a good and a bad run: gist.github.com/FROGGS/6a3d23f0b93db0a9938b 18:15
18:46 basiliscos joined
rurban Looks like a Parrot_pcc_reuse_continuation bug 19:34
19:36 zarchne joined
rurban very interesting, needs a ticket and a bisect probably 19:47
22:23 kid51 joined 22:31 Psyche^ joined