2025/08/01

Newest at the top

2025-08-01 20:34:15 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2025-08-01 20:33:59 +0200gorignak(~gorignak@user/gorignak) (Quit: quit)
2025-08-01 20:30:33 +0200puke(~puke@user/puke) puke
2025-08-01 20:27:24 +0200ljdarj1ljdarj
2025-08-01 20:27:24 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 272 seconds)
2025-08-01 20:26:15 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-08-01 20:23:16 +0200ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2025-08-01 20:20:01 +0200malte(~malte@mal.tc) malte
2025-08-01 20:18:16 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-08-01 20:15:10 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-08-01 20:14:45 +0200lxsameer(~lxsameer@Serene/lxsameer) (Ping timeout: 248 seconds)
2025-08-01 20:12:18 +0200malte(~malte@mal.tc) (Ping timeout: 276 seconds)
2025-08-01 20:03:39 +0200machinedgod(~machinedg@d75-159-126-101.abhsia.telus.net) (Ping timeout: 260 seconds)
2025-08-01 20:02:08 +0200malte(~malte@mal.tc) malte
2025-08-01 20:01:54 +0200malte(~malte@mal.tc) (Ping timeout: 276 seconds)
2025-08-01 20:00:15 +0200 <_d0t> i assume the people from #ghc are also here. And it's not that IRC is busy these days anyway.
2025-08-01 19:59:32 +0200 <merijn> lower traffic, less chance your question gets lost before anyone knowledgeable sees it :)
2025-08-01 19:59:08 +0200 <_d0t> ah ok, thanks
2025-08-01 19:59:01 +0200 <_d0t> merijn: correct
2025-08-01 19:59:00 +0200 <merijn> _d0t: Try #ghc that's where a lot of the GHC devs hang out for questions about hacking on the compiler/RTS itself
2025-08-01 19:58:36 +0200 <_d0t> sorry, bad keyboard
2025-08-01 19:58:30 +0200 <_d0t> *pass
2025-08-01 19:58:27 +0200 <_d0t> *can't find the RTS option to pas
2025-08-01 19:58:19 +0200 <_d0t> I have a custom GHC build and I did that. I just can
2025-08-01 19:58:18 +0200 <merijn> _d0t: I assume this means you're fiddling with GHC/RTS itself?
2025-08-01 19:58:06 +0200 <merijn> I suspect you have to link a debug RTS and I'm no sure if GHC ships with one by default
2025-08-01 19:57:25 +0200 <_d0t> also debugBelch and other similar stuff
2025-08-01 19:57:06 +0200 <_d0t> I mean the output of debugTrace calls in the C code of RTS
2025-08-01 19:56:42 +0200 <merijn> What do you mean by "in the RTS"?
2025-08-01 19:55:28 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 240 seconds)
2025-08-01 19:52:14 +0200caubert(~caubert@user/caubert) caubert
2025-08-01 19:51:27 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-08-01 19:50:58 +0200 <_d0t> ohai! How do I enable debug prints in RTS?
2025-08-01 19:46:50 +0200target_i(~target_i@user/target-i/x-6023099) target_i
2025-08-01 19:46:37 +0200heavens(~heavens@107.137.49.10) (Ping timeout: 265 seconds)
2025-08-01 19:46:12 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-08-01 19:45:54 +0200caubert(~caubert@user/caubert) (Ping timeout: 248 seconds)
2025-08-01 19:40:22 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-08-01 19:40:16 +0200gorignak(~gorignak@user/gorignak) gorignak
2025-08-01 19:39:07 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-08-01 19:38:52 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer)
2025-08-01 19:36:00 +0200 <heavens> :o
2025-08-01 19:35:41 +0200heavens(~heavens@107.137.49.10)
2025-08-01 19:34:32 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2025-08-01 19:29:29 +0200hakutaku(~textual@chen.yukari.eu.org)
2025-08-01 19:29:14 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-08-01 19:24:08 +0200tromp(~textual@2001:1c00:3487:1b00:5467:d1dd:5390:f8b9)
2025-08-01 19:22:53 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 245 seconds)
2025-08-01 19:19:26 +0200Guest22_(~textual@71.212.133.94)
2025-08-01 19:17:06 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds)