github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm Set by AlexDaniel on 12 June 2018. |
|||
00:28
TimToady joined
00:46
AlexDani` joined
00:47
AlexDani` is now known as AlexDaniel,
AlexDaniel left,
AlexDaniel joined
01:00
squashable6 left
01:02
squashable6 joined
01:15
TimToady left
01:16
TimToady joined
02:43
bloatable6 left,
releasable6 left,
squashable6 left,
undersightable6 left,
statisfiable6 left,
notable6 left,
unicodable6 left,
quotable6 left,
shareable6 left,
nativecallable6 left,
benchable6 left,
bisectable6 left,
committable6 left,
reportable6 left,
coverable6 left,
greppable6 left,
evalable6 left
02:44
squashable6 joined
02:45
releasable6 joined,
committable6 joined,
quotable6 joined,
benchable6 joined
02:46
bisectable6 joined,
unicodable6 joined,
undersightable6 joined,
nativecallable6 joined,
reportable6 joined,
shareable6 joined
02:47
coverable6 joined,
evalable6 joined
02:48
greppable6 joined,
statisfiable6 joined,
bloatable6 joined,
notable6 joined
03:04
lizmat left
03:13
squashable6 left
03:14
squashable6 joined
06:41
MasterDuke left
07:25
domidumont joined
08:02
lizmat joined
09:24
lizmat_ joined
09:27
lizmat left
11:36
lizmat_ is now known as lizmat
13:26
domidumont left,
domidumont joined
15:19
zakharyas joined
15:36
zakharyas left
15:41
domidumont left
15:51
zakharyas joined
16:11
patrickb joined
|
|||
Kaiepi | at some point in the future i'm thinking of auditing moarvm and using unveil(2) on openbsd wherever applicable to help make it more secure | 16:22 | |
thoughts? | |||
this explains what pledge(2) and unveil(2) do, though pledge is pretty useless in our case www.openbsd.org/papers/BeckPledgeU...an2018.pdf | |||
timotimo | sounds like a good idea | ||
Kaiepi | if moar were split into separate processes for networking, file i/o, and stuff pledge would be useful, but atm it's not so i'd just be enabling everything with it | 16:26 | |
timotimo | i haven't heard of unveil yet | 16:28 | |
Kaiepi | it's new to openbsd 6.4 i think | 16:29 | |
which is the current stable version | |||
6.5 is coming out soon, which is what i'm running | 16:30 | ||
patrickb | Kaiepi: I don't fully understand your last comment in r#2818 | 16:37 | |
yoleaux | 6 Apr 2019 23:10Z <jnthn> patrickb: GitHub organization invite sent; once you accept it you should have commit access. Welcome! :) | ||
synopsebot_ | R#2818 [open]: github.com/rakudo/rakudo/issues/2818 [BSD] Cannot run perl6 without using LD_LIBRARY_PATH on OpenBSD | ||
Kaiepi | gimme a sec patrickb, i'm in the middle of building rakudo for another issue i'm posting | ||
patrickb | no hurry | ||
timotimo | ok, so calling unveil once will make the entire filesystem except for one path disappear, and then you can put paths back with a limited rwxc | 16:41 | |
Kaiepi | yep | 16:50 | |
the difference in performance is pretty huge with MVM_JIT_DISABLE, to say the least | 16:54 | ||
i'm still building rakudo | |||
good work, jit team | |||
i don't mean that passive-aggressively, it's just one op jitted recently screwing things up that's making me use MVM_JIT_DISABLE | 17:09 | ||
17:13
AlexDani` joined
17:14
AlexDaniel left
|
|||
ugexe | what is he mystery op? | 17:16 | |
the^ | |||
you'd probably have to look at MVM_SPESH_LOG=log.txt output after it blows up | 17:17 | ||
17:18
domidumont joined
|
|||
Kaiepi | i'll find out when rakudo finishes building | 17:20 | |
17:26
MasterDuke joined,
MasterDuke left,
MasterDuke joined
|
|||
Kaiepi | ugexe, how do i tell which op is to blame? there are several expr bails | 17:29 | |
ugexe | i'd grep out the ops that bailed, filter to unique ops, then post the list from which i imagine we can identify any that were recently added | 17:30 | |
i dont know if this will actually work | 17:31 | ||
17:31
AlexDani` left
|
|||
ugexe | (MVM_SPESH_LOG=log.txt perl6 -e '...') && (cat log.txt|grep bail > log2.txt) && perl6 -e '.say for "log2.txt".IO.slurp.lines.map({ $_.match(/\s*(\w+) /)[0].Str }).unique.sort' | 17:33 | |
i dug that out of my bash history | |||
17:34
lizmat left
17:35
lizmat joined
|
|||
Kaiepi | ugexe, R#2824 | 17:45 | |
synopsebot_ | R#2824 [open]: github.com/rakudo/rakudo/issues/2824 Cannot install zef (or run much of anything without MVM_JIT_DISABLE) | ||
ugexe | hmm nothing sticking out. since it seems possibly file related i would take a guess that reverting github.com/MoarVM/MoarVM/commit/e1...259df30667 and rebulding moar might be worth a shot | 17:49 | |
17:54
AlexDani` joined
17:55
AlexDani` is now known as AlexDaniel,
AlexDaniel left,
AlexDaniel joined
|
|||
Kaiepi | ugexe, doesn't work | 18:03 | |
unveil(2) could possibly be responsible if something required to run perl6 uses it | 18:04 | ||
ugexe | you might have to manually bisect to figure it out | 18:05 | |
which i generally do by just reverting some commit halfway between last release, make install, run script to see if its still broke, then repeat | 18:06 | ||
MasterDuke | Kaiepi: does it work if you just use MVM_JIT_EXPR_DISABLE ? | ||
ugexe | its not `make install` for moarvm doesn't require rebuilding anything else | ||
s/not/nice/ | |||
s/reverting some commit/resetting to some commit/ | 18:08 | ||
18:11
MasterDuke left
|
|||
Kaiepi | .tell masterduke no it still segfaults | 18:11 | |
yoleaux | Kaiepi: I'll pass your message to masterduke. | ||
Kaiepi | .tell masterduke er, trace trap | ||
yoleaux | Kaiepi: I'll pass your message to masterduke. | ||
Kaiepi | for me it rebuilds everything whenever i reset to another commit ugexe | 18:13 | |
guess it depends on which make you're using | |||
ugexe | `make install` inside /MoarVM rebuilds rakudo (which is in another directory)? | 18:22 | |
i didnt expect the makefile to be aware of that | 18:23 | ||
Kaiepi | oh not rakudo | 18:47 | |
just moarvm | |||
wait am i supposed to rebuild nqp and moarvm after doing changes like reverting the fileno_fh jit templates ugexe? | |||
ugexe | just moarvm | 18:48 | |
Kaiepi | ok good because i didn't | ||
i reaaalllly don't wanna manually bisect two different bugs on code that spans across three repos | 18:49 | ||
i might write a script that takes a piece of code and does it for me | |||
ugexe | the number of repos is spans does not matter unless you encounter a commit that required an nqp bump | 18:51 | |
because you are just rebuilding moar and nothing else | |||
Kaiepi | the file errors may or may not be a bug in nqp or rakudo, i'm not sure yet | 18:52 | |
the trace trap i know is a legojit bug so it's not as annoying to bisect | |||
ugexe | well whatever it is happens during precomp | 18:56 | |
which creates files | |||
github.com/rakudo/rakudo/blob/5145...#L263-L286 | 18:57 | ||
perhaps you can use that to golf something | |||
19:16
domidumont left
|
|||
timotimo | the stacktrace from things called by the jit is usually completely unusable. as in, even when you think you see something in it, it's probably just leftovers/garbage that'll totally mislead you given the chance | 19:31 | |
20:08
discord6 left
20:13
discord6 joined,
discord6 left,
discord6 joined
21:02
zakharyas left
|
|||
Kaiepi | i figured, timotimo | 22:12 | |
timotimo | i can recommend rr to figure out what happens, but i'm not sure it runs on bsds | 22:13 | |
though rr isn't the only recording/replaying framework around, right? | |||
22:45
patrickb left
|
|||
ugexe | werent you saying something about using unveil or something now? | 22:58 | |
are you sure that 2019.03 worked under whatever conditions you have now? | 22:59 | ||
because what appears to me is that rakudo cant write to its site or home repositories | 23:00 | ||
when its trying to precomp | |||
and i'm not aware of anything since 2019.03 that should affect that |