MasterDuke and now i've gone even deeper and it looks like i need to create a src/6model/reprs/P6biguint.c 00:49
.ask jnthn if you look at my last couple comments/questions, could you tell me how far off the rails i've gone? thanks 01:15
yoleaux2 MasterDuke: I'll pass your message to jnthn.
06:54 domidumont joined
samcv MasterDuke, what are you referring to? 07:14
nwc10 jnthn: good *. The most exciting thing that happened all weekend (because it was the *only* think that happened all weekend): paste.scsys.co.uk/557459 08:41
why do my fingers typo it as "think" ? 08:42
08:48 brrt joined
brrt ohai #moarvm 08:48
jnthn I do that typo too... 09:58
yoleaux2 01:15Z <MasterDuke> jnthn: if you look at my last couple comments/questions, could you tell me how far off the rails i've gone? thanks
jnthn nwc10: How often does that happen?
I hope not "once in the whole weekend" :P
dogbert17_ is sad, the number of SEGV's are at an all time low :) 10:09
o/ btw 10:16
nwc10 once. in 3 days 10:23
jnthn Ouch. 10:24
dogbert17_ could it be the spesh bug? 10:34
jnthn I suspect so but...this is the only thing we've got that produces it, and it was already very rare 10:38
dogbert17_ how would one go about finding a bug like that?
given that a golf exists I mean 10:39
next qestion, are there any ENV vars or the like available with which you can perhaps make the probability of a bug showing itself increase? 10:50
jnthn MVM_SPESH_NODELAY=1 may make it more likely 11:21
Though under certain circumstances also risks hiding it 11:22
dogbert17_ thx, will try it out 12:02
dogbert17_ notes that 10 spectest files have failures when run with MVM_SPESH_NODELAY=1 12:13
brrt dogbert17_: interesting. what happens if you don't run MVM_SPESH_NODELAY, but you 'hotten' them? 12:15
dogbert17_ what is 'hotten' in this context, run a bunch of times? 12:16
brrt yes 12:26
well, within the same process 12:27
so that the thing will be speshed+jitted
dogbert17_ running e.g. './perl6 t/spec/S06-currying/misc.t' when MVM_SPESH_NODELAY=1 leads to the following
ok 9 - Priming :(::T $a, Array[Positional[T]] $b, Array[Positional[Int]] :$c) with \(1) gave :($b, Array[Positional[Int]] :$c)
Type check failed in binding to '$b'; expected Any but got T (?)
in any at ./blib/Perl6/BOOTSTRAP.moarvm line 1
brrt MVM_SPESH_NODELAY can expose bugs in spesh, but not necessarily the bug you're interested in or even one that could really happen 12:28
dogbert17_ ignore what I wrote above, had forgot to fudge :( 12:29
brrt, i'll try your suggestion if I'm unable to find anything directly :) 12:30
I liked jnthn's comment 'Though under certain circumstances also risks hiding it' 12:31
brrt, jnthn: here are the failing tests, perhaps a spesh bug might be hiding in there. gist.github.com/dogbert17/bbbeecfe...065758b16c 12:38
oh, 'ok 19 - &anonslurp.assuming((1, 2, "c", Bool::True).Seq)((Bool::True,).Seq) returned expected value ["a1 b2"] \n Segmentation fault' 13:14
brrt interesting 13:47
14:10 domidumont joined
dogbert17_ brrt: what do you make of this gdb outpout? gist.github.com/dogbert17/e0cd2b87...01b4982707 14:11
brrt flag is unitialized, or flag_map is 14:13
:-)
interesting
dogbert17_: can you print out the value of flag_map and flag 14:15
also 14:17
that looks like it's sensitive to env
i wonder how difficult it'd be to have 'shareable' debug sessions 14:18
either frozen (core dumps) or over the network
developers.googleblog.com/2017/03/...piled.html this is some impressive stuff, btw 14:21
14:26 domidumont joined
dogbert17_ brrt, sry was forced to do $work thingies :) 15:33
brrt well, that's important, innit 15:34
dogbert17_ (gdb) info locals # note this is from another run, had closed the previous session
flag = 0
flag_map = 0x3 <error: Cannot access memory at address 0x3>
brrt seems pretty likely that flag_map ain't initialized properly 15:36
dogbert17_ there seems to be something 'speshial' going on, unsetting the env var makes the test file pass 15:38
brrt well, that's not very special
the env var causes an extra allocation
dogbert17_ aha
brrt so something is being GC'ed without being fully initialized, it would seem
that's pretty weird, i think 15:39
dogbert17_ are you in a position to try it? Could perhaps be something fishy with my setup 15:41
brrt not really, not now 15:44
dogbert17_ am beginning to suspect that there's something on my end causing this ... 15:45
dogbert17_ but then again maybe not ... 16:28
dogbert17 jnthn: here's some ASAN output of what 'might' be a spesh bug: gist.github.com/dogbert17/8e96d144...a852f607d0 17:35
17:54 Ven joined 18:13 Ven joined
jnthn eww, that doesn't look to nice... 18:22
dogbert17: Normal nursery? 18:23
dogbert17 jnthn, yes
timotimo i've always had as neaking suspicion that callsite lifecycle management would end up problematic at some point 18:25
18:34 Ven joined
jnthn Aye, though I simplified it a bunch a while back 18:50
So not quite sure how it's going awry this time 18:51
dogbert17 on the plus side it should be easy to reproduce 18:53
18:53 Ven joined
timotimo i remember hoelzro struggled with callsites a while back. or maybe that was something else 19:00
hoelzro timotimo: I think so: hoelz.ro/blog/hunted-by-a-leak 19:07
19:13 Ven joined
[Coke] hoelzro: I cannot tell when that published. :( 19:17
timotimo oh, indeed
that's a pet-peeve of mine
when you can't tell what the date on a blog post/article/whatever is 19:18
[Coke] reads all the entries, though, nifty 19:19
hoelzro++ fixing things and taking names.
19:24 agentzh joined 19:33 Ven joined
hoelzro oh - maybe I should add that, then? 19:37
I read a post once that said you *shouldn't* do that
timotimo huh? 19:38
tell me where the author lives, i'll fight them irl!
hoelzro timotimo: training.kalzumeus.com/newsletters...g-strategy
[Coke] hoelzro: My best counter example is anything involving rakudo on parrot. You wouldn't want someone to think they were reading the state of the art. 19:39
hoelzro that's a really good point
timotimo "content marketing strategy"
>_>
hoelzro and considering how fast Moar moves...
timotimo: it was linked from a post about writing a great programming blog
timotimo if your goal is to make people think your stuff is still relevant by just not telling them when it was written ...
hoelzro ...which mine is not, so... 19:40
maybe I
maybe I'll just add those date.
*dates
jeez
can't type today!
nwc10 it's all the fault of the DST switch? 19:41
(I forget exactly where you are, but I was thinking the US, but also know that not all parts of the US do the DST dance) 19:42
[Coke] dumb dumb DST. :|
nwc10 UGT to UGT+1
I'm not sure how/if that works
[Coke] wonders how amenable NYS would be to a "kill DST" bill.
nwc10 it's somewhat like ∞ + 1 19:43
hoelzro I did indeed do the DST dance =( 19:44
ok, publish dates added 19:47
...at the bottom - adding them in a nice place on the top will likely take a little more work
19:53 Ven joined
[Coke] thinks that's fine. 19:56
lizmat datapoint: I haven't been able to crash HARNESS_TYPE=6 make spectest after 30 runs 19:59
nwc10 I haven't been able to crash it for 48 hours now 20:01
it's looking good
timotimo <3 20:07
20:13 Ven joined
timotimo oooh, the gdb-moar.py can benefit seriously from the debug name featuer 20:19
feature*
20:33 Ven joined 20:53 Ven joined 21:05 Ven joined 21:57 zakharyas joined
samcv good * 22:05
lizmat samcv o/
samcv i'm feeling kind of like writing a case insensitive index op today 22:07
lizmat samcv: go for it! :-) 22:10

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!