Newest at the top
| 2025-12-28 02:24:56 +0100 | divlamir | (~divlamir@user/divlamir) divlamir |
| 2025-12-28 02:24:44 +0100 | divlamir | (~divlamir@user/divlamir) (Read error: Connection reset by peer) |
| 2025-12-28 02:21:29 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 02:19:36 +0100 | hsw_ | (~hsw@112-104-86-252.adsl.dynamic.seed.net.tw) (Remote host closed the connection) |
| 2025-12-28 02:19:21 +0100 | hsw_ | (~hsw@112-104-86-252.adsl.dynamic.seed.net.tw) hsw |
| 2025-12-28 02:18:55 +0100 | hsw | (~hsw@112-104-86-252.adsl.dynamic.seed.net.tw) hsw |
| 2025-12-28 02:17:35 +0100 | omidmash2 | omidmash |
| 2025-12-28 02:17:35 +0100 | omidmash | (~omidmash@user/omidmash) (Ping timeout: 244 seconds) |
| 2025-12-28 02:16:19 +0100 | collide2954 | (~collide29@user/collide2954) collide2954 |
| 2025-12-28 02:15:46 +0100 | omidmash2 | (~omidmash@user/omidmash) omidmash |
| 2025-12-28 02:14:10 +0100 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2025-12-28 02:12:50 +0100 | Hafydd | (~Hafydd@user/hafydd) (Quit: WeeChat 4.8.1) |
| 2025-12-28 02:11:58 +0100 | <int-e> | presumably this is about ARM's "pointer authentication" feature |
| 2025-12-28 02:10:21 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-12-28 02:07:05 +0100 | <geekosaur> | (that said, I think memcheck has superseded all of them…) |
| 2025-12-28 02:06:04 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 02:04:57 +0100 | <geekosaur> | they're really nice in conjunction with debuggers because you can break on the error entry point and catch things like that immediately instead of after something reveals memory corruption |
| 2025-12-28 02:03:06 +0100 | <geekosaur> | which doesn't mean you can't segfault on them, just that common errors like double free, use after free, and overreading/writing a block are detected and reported instead of corrupting memory or crashing |
| 2025-12-28 02:02:08 +0100 | <geekosaur> | there are malloc libraries which do that (it's not up to the hardware) |
| 2025-12-28 01:58:18 +0100 | collide2954 | (~collide29@user/collide2954) (Quit: The Lounge - https://thelounge.chat) |
| 2025-12-28 01:54:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-12-28 01:50:16 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 01:39:21 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-12-28 01:37:06 +0100 | mhatta | (~mhatta@www21123ui.sakura.ne.jp) (Quit: ZNC 1.10.1+deb1 - https://znc.in) |
| 2025-12-28 01:34:28 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 01:33:29 +0100 | <haskellbridge> | <Liamzee> we ended up having to point a pointer at kernel memory just to trigger a segfault |
| 2025-12-28 01:33:04 +0100 | <haskellbridge> | <Liamzee> apparently apple silicon (and psosibly modern ARM in general) is designed to be very resistant to segfaults; double free would throw an error, but not a segfault |
| 2025-12-28 01:24:01 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-12-28 01:19:01 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 01:11:34 +0100 | peterbecich | (~Thunderbi@71.84.33.135) (Ping timeout: 246 seconds) |
| 2025-12-28 01:11:25 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-12-28 01:06:26 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 01:01:15 +0100 | hsw | (~hsw@112-104-86-252.adsl.dynamic.seed.net.tw) (Ping timeout: 240 seconds) |
| 2025-12-28 00:55:19 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-12-28 00:50:37 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 00:39:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-12-28 00:36:32 +0100 | peterbecich | (~Thunderbi@71.84.33.135) peterbecich |
| 2025-12-28 00:35:11 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 00:27:07 +0100 | vetkat | (~vetkat@user/vetkat) vetkat |
| 2025-12-28 00:26:43 +0100 | vetkat | (~vetkat@user/vetkat) (Read error: Connection reset by peer) |
| 2025-12-28 00:23:02 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-12-28 00:18:19 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 252 seconds) |
| 2025-12-28 00:18:01 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 00:14:36 +0100 | bitdex_ | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-12-28 00:11:06 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-12-28 00:06:38 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-28 00:05:03 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-12-28 00:01:15 +0100 | bitdex_ | (~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection) |
| 2025-12-27 23:56:07 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-12-27 23:56:02 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) ChaiTRex |