Newest at the top
| 2026-02-11 22:10:55 +0100 | emmanuelux | (~em@user/emmanuelux) emmanuelux |
| 2026-02-11 22:07:55 +0100 | tromp | (~textual@2001:1c00:3487:1b00:5913:697:5f95:d198) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2026-02-11 22:06:55 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) ChaiTRex |
| 2026-02-11 22:06:29 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Remote host closed the connection) |
| 2026-02-11 22:05:44 +0100 | califax | (~califax@user/califx) califx |
| 2026-02-11 22:05:28 +0100 | califax | (~califax@user/califx) (Remote host closed the connection) |
| 2026-02-11 22:04:49 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds) |
| 2026-02-11 22:01:54 +0100 | <brioche> | I could do this by disabling close_fds in CreateProcess, but I don't want the other FDs to stay open. I just want to keep a specific list of FDs open. |
| 2026-02-11 22:00:33 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-11 22:00:18 +0100 | <brioche> | Yeah, a pipe for example |
| 2026-02-11 21:58:41 +0100 | <EvanR> | the other FDs? |
| 2026-02-11 21:57:11 +0100 | Googulator54 | Googulator |
| 2026-02-11 21:55:56 +0100 | <brioche> | I know that createProcess allows to specify a stdin, stdout and stderr FDs, but what about the other FDs? |
| 2026-02-11 21:55:22 +0100 | <brioche> | Does anyone here know how to spawn a process with a given specific file descriptor? |
| 2026-02-11 21:50:17 +0100 | Googulator | (~Googulato@2a01-036d-0106-216f-6164-ec92-51a0-9cde.pool6.digikabel.hu) (Ping timeout: 272 seconds) |
| 2026-02-11 21:50:03 +0100 | brioche | (~username@user/brioche) brioche |
| 2026-02-11 21:49:53 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2026-02-11 21:45:56 +0100 | Googulator54 | (~Googulato@84-236-65-138.pool.digikabel.hu) |
| 2026-02-11 21:45:09 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-11 21:43:57 +0100 | divlamir | (~divlamir@user/divlamir) divlamir |
| 2026-02-11 21:43:41 +0100 | divlamir | (~divlamir@user/divlamir) (Read error: Connection reset by peer) |
| 2026-02-11 21:34:49 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-02-11 21:30:45 +0100 | <perryprog> | nuke did not fix :( |
| 2026-02-11 21:29:46 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-11 21:21:51 +0100 | target_i | (~target_i@user/target-i/x-6023099) target_i |
| 2026-02-11 21:16:32 +0100 | Enrico63 | (~Enrico63@host-79-22-157-220.retail.telecomitalia.it) (Quit: Client closed) |
| 2026-02-11 21:13:04 +0100 | <perryprog> | well, yes |
| 2026-02-11 21:12:59 +0100 | <EvanR> | so the entire body of the program can a priori be implicated |
| 2026-02-11 21:12:29 +0100 | <EvanR> | I don't think code knows what a line is... it's about the values being passed to the e.g. readCreateProcessWithExitCode... or some FFI call, because if there is corruption the crash can easily be non-locally triggered |
| 2026-02-11 21:11:39 +0100 | <perryprog> | intermediate bug theorem is hilarious |
| 2026-02-11 21:11:31 +0100 | <perryprog> | the problem lines of code are literally identical :( |
| 2026-02-11 21:11:05 +0100 | <EvanR> | slowly mutate the non working one to the working one, and eventually it has to flip. (intermediate bug theorem) |
| 2026-02-11 21:10:22 +0100 | <EvanR> | same version different projects different results... even after cloning them and rebuilding everything, then it really seems like you have more usage patterns to bisect |
| 2026-02-11 21:09:48 +0100 | pr1sm | (~pr1sm@24.91.163.31) (Remote host closed the connection) |
| 2026-02-11 21:09:11 +0100 | peterbecich | (~Thunderbi@71.84.33.135) (Ping timeout: 252 seconds) |
| 2026-02-11 21:09:11 +0100 | <perryprog> | mebbe we do a nuke |
| 2026-02-11 21:07:29 +0100 | <EvanR> | /o\ |
| 2026-02-11 21:05:10 +0100 | <perryprog> | annnnd fixxing it to 1.6.25.0 still sees a segfault in the non-working project |
| 2026-02-11 21:04:31 +0100 | <EvanR> | \o/ |
| 2026-02-11 21:02:33 +0100 | <perryprog> | presumably 1.6.25.0 works, 1.6.26.1 doesn't |
| 2026-02-11 21:02:10 +0100 | <perryprog> | they're different versions :) |
| 2026-02-11 21:01:22 +0100 | <EvanR> | then delete the freeze file |
| 2026-02-11 21:00:59 +0100 | <EvanR> | try doing cabal freeze and looking at the freeze file |
| 2026-02-11 20:57:54 +0100 | pr1sm | (~pr1sm@24.91.163.31) |
| 2026-02-11 20:53:25 +0100 | <perryprog> | I checked via cabal list --installed; is that correct? |
| 2026-02-11 20:51:40 +0100 | <EvanR> | same version, different results, I daresay it's not the package |
| 2026-02-11 20:47:49 +0100 | fgarcia | (~lei@user/fgarcia) (Ping timeout: 265 seconds) |
| 2026-02-11 20:46:09 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2026-02-11 20:45:12 +0100 | Googulator | (~Googulato@2a01-036d-0106-216f-6164-ec92-51a0-9cde.pool6.digikabel.hu) |
| 2026-02-11 20:44:57 +0100 | Googulator | (~Googulato@2a01-036d-0106-216f-6164-ec92-51a0-9cde.pool6.digikabel.hu) (Quit: Client closed) |