|
00:20
itaipu left
00:46
itaipu joined
01:26
itaipu left
|
|||
| disbot11 | <.landyacht.> Hm, Rakudo is sucking memory and CPU on startup and not even printing a statement I put in a BEGIN phaser... any tricks for diagnosing this? I almost suspect something with precompilation, but I don't know how one disables that | 01:47 | |
| <.landyacht.> yeah, even running with -c flag does this | 01:49 | ||
|
01:49
itaipu joined
02:15
kylese left
02:16
kylese joined
02:20
sibl joined
|
|||
| Voldenet | Probably some compilation issue | 02:36 | |
| the only way to debug it would be probably using gdb | |||
| breaking and printing stack at some point :\ | 02:37 | ||
| I'm betting infinite recursion because that's the easiest way to get this | |||
| since you don't need to even run the code, consider golfing | 02:38 | ||
|
03:05
annamalai joined
03:15
kylese left,
kylese joined
03:21
vasko4535586 left
03:22
vasko4535586 joined
|
|||
| disbot11 | <.landyacht.> yeah I'm working on a pretty large application and given the vague nature of the problem idk where to start with tracking down a golf :/ | 03:44 | |
| <.landyacht.> I'll give gdb a try, haven't used that in ages | |||
|
04:15
sibl left
04:35
lichtkind__ joined
04:38
lichtkind_ left
05:06
stanrifkin joined
|
|||
| Voldenet | Hm, maybe there's a way of getting a stack from rakudo itself | 05:24 | |
| if the app is truly large but modular then maybe RAKUDO_MODULE_DEBUG=1 would help somehow | 05:29 | ||
| so, you may need to use `call (void)MVM_dump_backtrace(tc)` in gdb | 05:37 | ||
|
06:13
johnjay joined
|
|||