|
github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm Set by AlexDaniel on 12 June 2018. |
|||
|
01:06
AlexDani` joined
01:10
AlexDaniel left
03:11
squashable6 left
03:12
squashable6 joined
04:58
squashable6 left
05:04
squashable6 joined
07:16
avar left,
avar joined,
avar left,
avar joined
07:20
patrickb joined
07:27
domidumont joined
08:00
zakharyas joined
08:22
MasterDuke left
10:03
sena_kun joined,
zakharyas left
10:07
domidumont left
11:49
domidumont joined
12:27
zakharyas joined
13:20
sena_kun left,
sena_kun joined
13:25
sena_kun left,
sena_kun joined
13:58
zakharyas left
14:03
zakharyas joined
14:19
pamplemousse joined
14:20
AlexDani` is now known as AlexDaniel,
AlexDaniel left,
AlexDaniel joined
14:21
sena_kun left
|
|||
| dogbert11 | timotimo: do you want me to make a PR of the misplaced line here (github.com/MoarVM/MoarVM/blob/mast...og.c#L106) or will you fix it? | 15:06 | |
| timotimo | which of y'all found it and gets the ++ in the commit message? | 15:08 | |
| dogbert11 | give it to MasterDuke :) | 15:23 | |
|
15:26
patrickb left
|
|||
| Geth | MoarVM: 459e686754 | (Timo Paulssen)++ | src/profiler/log.c Remove confprog effects when confprog isn't active MasterDuke++ found this |
15:29 | |
|
15:29
domidumont left
15:34
domidumont joined
15:55
brrt joined
16:44
brrt left
16:56
pamplemousse left
17:22
pamplemousse joined
17:28
domidumont left
17:36
lucasb joined
17:47
brrt joined
18:12
brrt left,
brrt joined
|
|||
| brrt | \o | 18:36 | |
| pamplemousse | o/ | 18:38 | |
|
18:41
zakharyas left
|
|||
| brrt | hmm, I get the same 'ModuleLoader.moarvm' problem when I use a slightly more complex NQP file as input source | 18:42 | |
| but, I don't get that problem if I set '--libpath' correctly | 18:43 | ||
| pamplemousse: I was actually going to suggest, you can try strace to figure out what the program is doing when it's starting up | 18:45 | ||
| pamplemousse | I can give that a go. I've been tracing through using MVM_COVERAGE_LOG, like timotimo suggested the other day, to figure out how the start up worked | 18:50 | |
|
19:37
MasterDuke joined
|
|||
| brrt | that, or stepping through with gdb/lldb | 20:02 | |
| timotimo | right, you can always "call MVM_dump_backtrace(tc)" from inside gdb/lldb (if you "up" far enough to get a frame with a tc in it; that part is easier if you disable the JIT, because neither gdb nor lldb understand how the jit builds stack frames | 20:05 | |
| brrt | which is what I should probably fix at some time | 21:07 | |
|
21:12
pamplemousse left
21:13
pamplemousse joined
21:16
brrt left
21:41
pamplemousse left
22:07
MasterDuke left
22:31
ggoebel left
23:29
rba left
|
|||