|
00:13
vendethiel- joined
01:47
ilbot3 joined
02:15
vendethiel joined
03:21
zostay_ joined
03:23
ilmari_ joined
03:24
khagan_ joined
03:26
dalek joined,
synopsebot6 joined
03:28
geekosaur joined
09:21
doublec left
11:42
Ven joined
12:10
Ven joined
13:57
Ven joined
15:37
Ven joined
16:05
vendethiel joined
16:18
lizmat joined
17:18
domidumont joined
17:23
domidumont joined
18:45
domidumont joined
19:05
avuserow joined
|
|||
| avuserow | I ran into a double free or memory corruption error on some code on moar yesterday. Is github issues an okay place for this? (Wanted to make sure that it wasn't a potential security bug that should be directed elsewhere) | 19:10 | |
| jnthn | avuserow: The GitHub issues queue should be fine; thanks for asking. | 19:16 | |
| And thanks in advance for reporting :) | |||
| avuserow | jnthn: not a problem. let me know if you want me to run it under gdb or valgrind or anything like that. I'm attempting to golf it down a bit now. | 19:28 | |
| jnthn | avuserow: Does it involve a multi-threaded program? | ||
| avuserow | no, I'm not using any constructs like that | 19:30 | |
| jnthn | Hm, OK | 19:35 | |
|
19:36
ggoebel joined
|
|||
| jnthn | And golfing is very helpful/welcome. :) | 19:39 | |
| avuserow | bug report filed. The golfed code only seems to fail on the initial revision, so I also attached ungolfed code which fails on a ~30 minute old rebuild. | 20:04 | |
|
21:39
pyrimidine joined
22:30
zostay joined
23:43
mtj_ joined
23:55
tomboy65 joined
|
|||