Perl 6 - the future is here, just unevenly distributed

IRC log for #moarvm, 2016-12-18

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:03 pyrimidine joined #moarvm
00:20 pyrimidine joined #moarvm
00:59 timotimo so ... i'm apparently trying to reproduce the memory leak that comes from not setting foreign_memory back to 0 ...
00:59 timotimo i think i'm not doing it right
00:59 timotimo maybe 100 evals aren't enough, or the code inside isn't complex enough
01:03 TimToady You have to do it with an eval laugh!
01:04 timotimo ==25821== 0 bytes in 37,312 blocks are definitely lost in loss record 1 of 46
01:04 timotimo um ... what?
01:05 timotimo i mean, yeah, it's the function that's supposed to be leaking
01:05 timotimo but ... how
01:06 geekosaur it thinks something else is referencing that memory
01:06 timotimo um, so how is it "definitely lost", then?
01:06 timotimo oh
01:06 geekosaur 0 bytes definitely lost
01:06 timotimo right!
01:07 geekosaur the final summary includes memory that it thinks *might* be lost, but until then it doesn't know for certain
01:07 geekosaur and even then it can't be 100% certain but has some notion of what might be an indirect leak
01:07 timotimo well, yeah, of course
01:08 timotimo you might have sent the pointer to the exact memory location off to a hidden server in the maledives
01:11 geekosaur to some extent, "pointer" is not a concrete thing that can be 100% reliably identified. especially when you are writing a garbage collector! it may do things that cause the emulator to wonder if it's really a pointer or not, so then you have X amount of memory that might be lost through something that it's not sure is a pointer or not
01:12 timotimo right
01:12 geekosaur depending on how the gc is written (and how clever the emulator's heuristics are) it may be more or less certain. if you managed to hit one of the "less certain" cases here, memcheck might be out of its depth
01:13 timotimo this isn't gc-managed memory, though :)
01:13 timotimo but i suppose gc-managed memory used to point to it
02:48 ilbot3 joined #moarvm
02:48 Topic for #moarvm is now https://github.com/moarvm/moarvm | IRC logs at  http://irclog.perlgeek.de/moarvm/today
05:33 pyrimidine joined #moarvm
05:46 nebuchadnezzar joined #moarvm
06:35 pyrimidine joined #moarvm
07:20 domidumont joined #moarvm
07:25 domidumont joined #moarvm
07:35 pyrimidine joined #moarvm
08:29 domidumont joined #moarvm
08:36 pyrimidine joined #moarvm
08:45 pyrimidine joined #moarvm
08:54 pyrimidine joined #moarvm
09:23 pyrimidine joined #moarvm
09:35 pyrimidine joined #moarvm
09:42 pyrimidine joined #moarvm
10:00 pyrimidine joined #moarvm
10:10 pyrimidine joined #moarvm
10:28 pyrimidine joined #moarvm
10:38 pyrimidine joined #moarvm
10:47 pyrimidine joined #moarvm
11:05 pyrimidine joined #moarvm
11:15 pyrimidine joined #moarvm
11:33 pyrimidine joined #moarvm
11:41 pyrimidine joined #moarvm
11:43 pyrimidi_ joined #moarvm
11:59 pyrimidine joined #moarvm
12:03 FROGGS joined #moarvm
12:11 pyrimidine joined #moarvm
12:18 pyrimidine joined #moarvm
12:38 pyrimidine joined #moarvm
12:48 pyrimidine joined #moarvm
12:57 pyrimidine joined #moarvm
13:16 pyrimidine joined #moarvm
13:25 pyrimidine joined #moarvm
13:35 pyrimidine joined #moarvm
13:43 pyrimidi_ joined #moarvm
14:18 pyrimidine joined #moarvm
14:45 pyrimidine joined #moarvm
15:12 pyrimidine joined #moarvm
15:13 nebuchadnezzar joined #moarvm
15:24 pyrimidine joined #moarvm
15:43 pyrimidine joined #moarvm
15:49 pyrimidine joined #moarvm
16:15 pyrimidine joined #moarvm
16:25 pyrimidine joined #moarvm
16:45 pyrimidine joined #moarvm
16:55 pyrimidine joined #moarvm
16:58 * dogbert17 deafening silence
16:58 timotimo hey dogbert, what's up?
16:59 dogbert17 hi timotimo, as always I have a suspicious gist :-)
16:59 dogbert17 is this RT or a MoarVM issue? https://gist.github.com/dogbert17/dca0295c16d77b2ff4ae4be19a6f8279
17:01 timotimo ah, that one. i have no idea :|
17:02 timotimo i do see that we don't compile uv with debug info when moar's configure has debug turned on, apparently
17:02 timotimo i wonder how to tell what stack frame the address belongs to
17:03 dogbert17 when I run it now I also get this: moar: 3rdparty/libuv/src/uv-common.c:624: uv_loop_delete: Assertion `err == 0' failed.
17:04 timotimo how nice, it doesn't tell us what the error is, of course
17:04 pyrimidine joined #moarvm
17:05 dogbert17 seems to come from: void uv_loop_delete(uv_loop_t* loop) { ...
17:07 timotimo right
17:07 timotimo but it doesn't say what err is, other than "not 0"
17:07 timotimo which is like "terminating because of an error: error."
17:08 dogbert17 I'll see if I can catch it somehow
17:09 timotimo gdb should be of help
17:09 timotimo if you break on the assertion or something
17:09 timotimo also, maybe you can/have to put -g3 into the CFLAGS inside libuv's Makefile
17:11 dogbert17 tryin to set a breakpoint in gdb didn't work. maybe I need this flag of yours then
17:12 timotimo yeah, if it's compiled without debug symbols (as the lack of line numbers in the backtrace suggests) it won't let you do most interesting things
17:13 dogbert17 hmm, which file is the makefile, there are several, hmm
17:14 timotimo good question; i don't know much about how libuv is built
17:14 timotimo maybe the internet knows
17:20 domidumont joined #moarvm
17:23 pyrimidine joined #moarvm
17:33 pyrimidine joined #moarvm
17:49 pyrimidi_ joined #moarvm
18:09 dogbert17 FROGGS: you around?
18:27 * dogbert17 after a lot of tinkering, the error code is -16, the problem only occurs with the --full-cleanup option
18:35 timotimo ah
18:35 timotimo well, full-cleanup issues aren't as bad
18:42 FROGGS dogbert17: I am
18:46 dogbert17 FROGGS: I was going to ask about a lib uv assertion failure (backlog a page) but it seems to occur when running with --full-cleanup so maybe it's not important
18:49 FROGGS dogbert17: yeah, seen it a minute ago... I've no clue what we can/should do
18:51 dogbert17 I believe that both timotimo and jnthn has said that --full-cleanup is a bit broken, so maybe the error is caused by some less optimal cleanup code
19:04 pyrimidine joined #moarvm
19:16 pyrimidine joined #moarvm
19:41 mst joined #moarvm
19:42 pyrimidine joined #moarvm
19:46 domidumont joined #moarvm
19:56 pyrimidine joined #moarvm
20:13 dalek joined #moarvm
20:20 pyrimidine joined #moarvm
20:32 pyrimidine joined #moarvm
20:45 pyrimidine joined #moarvm
21:09 pyrimidine joined #moarvm
21:21 pyrimidine joined #moarvm
21:40 pyrimidine joined #moarvm
21:51 pyrimidine joined #moarvm
22:00 pyrimidine joined #moarvm
22:20 pyrimidine joined #moarvm
22:30 pyrimidine joined #moarvm
22:31 dalek MoarVM/compunit_string_mem_share: 549e7d5 | timotimo++ | src/ (4 files):
22:31 dalek MoarVM/compunit_string_mem_share: Revert "Revert "share some string's memory with compunit memory""
22:31 dalek MoarVM/compunit_string_mem_share:
22:31 dalek MoarVM/compunit_string_mem_share: This reverts commit b8f72297ba13736efb7e01b28d199b158b18d7df.
22:31 dalek MoarVM/compunit_string_mem_share: review: https://github.com/MoarVM/MoarVM/commit/549e7d565e
22:31 dalek MoarVM/compunit_string_mem_share: 406fa15 | timotimo++ | src/6model/reprs/MVMCompUnit.c:
22:31 dalek MoarVM/compunit_string_mem_share: Revert "Revert "prevent access to un-deserialized strings in gc_free""
22:31 dalek MoarVM/compunit_string_mem_share:
22:31 dalek MoarVM/compunit_string_mem_share: This reverts commit 47629f3230b784de52f66de19c97f3d3e1e1f29e.
22:31 dalek MoarVM/compunit_string_mem_share: review: https://github.com/MoarVM/MoarVM/commit/406fa15201
22:31 dalek MoarVM/compunit_string_mem_share: c85c15f | timotimo++ | src/6model/reprs/MVMCompUnit.c:
22:31 dalek MoarVM/compunit_string_mem_share: make sure previously shared strings get freed
22:48 pyrimidine joined #moarvm
22:50 pyrimidi_ joined #moarvm
23:09 pyrimidine joined #moarvm
23:10 SmokeMachine joined #moarvm
23:12 SmokeMachine hi there! I got a segfault trying to run my perl6 code: https://gist.github.com/FCO/bb1bb1c0285fcfa12d8f2d8789beb21f
23:12 SmokeMachine it occurs some times...
23:13 SmokeMachine but my code is very big... I'm trying to reduce it...
23:22 pyrimidine joined #moarvm
23:47 pyrimidine joined #moarvm
23:50 d4l3k_ joined #moarvm
23:59 pyrimidine joined #moarvm

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary