2022-04-14 00:07:23 +0200 | ectospasm | (~ectospasm@user/ectospasm) (Quit: WeeChat 3.5) |
2022-04-14 00:10:03 +0200 | ectospasm | (~ectospasm@user/ectospasm) |
2022-04-14 00:52:58 +0200 | <abastro[m]> | I realized the problem I recognized with taffybar |
2022-04-14 00:53:12 +0200 | <abastro[m]> | It doesn't work on 9.2.2 :P |
2022-04-14 01:05:41 +0200 | <geekosaur> | but it compiles? that would be odd |
2022-04-14 01:06:38 +0200 | <abastro[m]> | It does not compile |
2022-04-14 01:07:08 +0200 | <abastro[m]> | One of the file has FlexibleContexts but not FlexibleInstances extension |
2022-04-14 01:07:18 +0200 | <abastro[m]> | That one file breaks everything |
2022-04-14 01:07:33 +0200 | <abastro[m]> | Eh, I guess it is more a gripe towards ghc breaking changes |
2022-04-14 01:11:28 +0200 | Artus | (~Artus@190.192.80.102) |
2022-04-14 02:43:07 +0200 | benin | (~benin@183.82.204.110) (Ping timeout: 240 seconds) |
2022-04-14 03:10:06 +0200 | Artus | (~Artus@190.192.80.102) (Ping timeout: 250 seconds) |
2022-04-14 03:45:33 +0200 | <abastro[m]> | I hate when ghc9.2.2 is unstable so my xmonad randomly crashes once a week |
2022-04-14 03:57:57 +0200 | <davean> | abastro[m]: What bugs are you encountering with GHC 9.2.2? |
2022-04-14 03:58:19 +0200 | <abastro[m]> | It randomly crashes, I cannot find more details |
2022-04-14 03:58:34 +0200 | <abastro[m]> | Idk where to find the crash dump file, if it exists |
2022-04-14 03:58:43 +0200 | <abastro[m]> | Log does not report anything in particular |
2022-04-14 03:58:59 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
2022-04-14 04:03:36 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 248 seconds) |
2022-04-14 04:05:03 +0200 | bla | (~bla@79.191.74.133.ipv4.supernova.orange.pl) (Ping timeout: 260 seconds) |
2022-04-14 04:15:21 +0200 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving) |
2022-04-14 04:15:30 +0200 | bla | (~bla@79.191.254.193.ipv4.supernova.orange.pl) |
2022-04-14 04:18:53 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
2022-04-14 04:21:54 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
2022-04-14 04:47:40 +0200 | terrorjack | (~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat) |
2022-04-14 04:50:06 +0200 | terrorjack | (~terrorjac@2a01:4f8:1c1e:509a::1) |
2022-04-14 05:00:29 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds) |
2022-04-14 05:39:56 +0200 | matijja | (~matijja@193.77.181.201) (Quit: ZNC 1.8.2 - https://znc.in) |
2022-04-14 05:43:12 +0200 | matijja | (~matijja@193.77.181.201) |
2022-04-14 07:29:48 +0200 | benin | (~benin@183.82.204.110) |
2022-04-14 07:58:12 +0200 | <Solid> | I again seriously doubt this is GHC's fault |
2022-04-14 07:58:33 +0200 | <Solid> | and that taffybar stuff sounds like an easy fix |
2022-04-14 07:58:50 +0200 | <Solid> | so how about you prepare a PR instead of complaining that it doesn't work and you know how to fix it? :> |
2022-04-14 07:59:45 +0200 | <abastro[m]> | Solid: I guess how I said it was a bit confusing |
2022-04-14 08:00:43 +0200 | <abastro[m]> | Taffybar one was a trivial fix of just cloning, tho it comes from breaking change by ghc. |
2022-04-14 08:01:17 +0200 | <abastro[m]> | The random crash stuff is something else, a phenomenon that began occurring after updating to 9.2 2 |
2022-04-14 08:02:50 +0200 | <Solid> | if you have a proper reproducer then by all means report it to GHCs issues |
2022-04-14 08:03:22 +0200 | <Solid> | (as for the breaking change... there's is an automatic upgrade path, so I wouldn't even count that tbh) |
2022-04-14 08:04:00 +0200 | <abastro[m]> | Wdym automatic upgrade path? |
2022-04-14 08:05:48 +0200 | <Solid> | "if FlexibleContexts is on in this file but not FlexibleInstances, add FlexibleInstances" |
2022-04-14 08:05:59 +0200 | <Solid> | sounds like something a computer is good at! |
2022-04-14 08:20:25 +0200 | <abastro[m]> | Eh, I mean, that will generate warnings for files that does not apply |
2022-04-14 08:20:44 +0200 | <abastro[m]> | Then imagine -Werror |
2022-04-14 08:20:53 +0200 | <abastro[m]> | ..wait was redundant extension not a warning |
2022-04-14 08:23:27 +0200 | <Solid> | if it's only a warning then it's even more "not even a breaking change" |
2022-04-14 08:23:38 +0200 | <abastro[m]> | Anyway the bigger problem was that the author is not inclined to even update package on hackage to a version with a bug fixed |
2022-04-14 08:24:16 +0200 | <abastro[m]> | Solid: I mean, with FlexibleInstances and without FlexibleContexts, it is error |
2022-04-14 08:25:02 +0200 | <Solid> | AFAIK Hackage trustees can update packages with small fixes like that |
2022-04-14 08:25:12 +0200 | <abastro[m]> | Also I was wrong with warning for redundant extension |
2022-04-14 08:25:48 +0200 | <abastro[m]> | Author is alive and well, the author promised to upload the fix on hackage |
2022-04-14 08:26:05 +0200 | <abastro[m]> | And that does not happen :p |
2022-04-14 08:29:09 +0200 | <Solid> | use the git version in the meantime :) |
2022-04-14 08:29:33 +0200 | <abastro[m]> | Yep |
2022-04-14 08:29:51 +0200 | <abastro[m]> | Anyway that is more or less trivial probelm |
2022-04-14 08:30:16 +0200 | m5zs7k | (aquares@web10.mydevil.net) (Ping timeout: 248 seconds) |
2022-04-14 08:30:19 +0200 | <abastro[m]> | Bigger one was with unidentifiable xmonad random crash, it doesn't even reproduce reliably |
2022-04-14 08:30:23 +0200 | <abastro[m]> | It's just random |
2022-04-14 08:30:25 +0200 | <abastro[m]> | Meh |
2022-04-14 08:30:51 +0200 | m5zs7k | (aquares@web10.mydevil.net) |
2022-04-14 08:34:32 +0200 | cfricke | (~cfricke@user/cfricke) |
2022-04-14 09:19:28 +0200 | smashgra_ | (~smashgrab@bare.metal.computer) (Quit: ZNC 1.7.2+deb3 - https://znc.in) |
2022-04-14 09:19:46 +0200 | smashgrab | (~smashgrab@bare.metal.computer) |
2022-04-14 09:33:32 +0200 | <geekosaur> | Solid, Hackage trustees can only do version bounds changes in the cabal file, not actual package changes |
2022-04-14 09:35:01 +0200 | <Solid> | oh I see |
2022-04-14 09:36:10 +0200 | <Ether[m]> | I dont why but it seems XMonad.Layout.Fullscreen does have a way to add a binding.. |
2022-04-14 09:36:43 +0200 | <geekosaur> | because it's up to the app, which often dpoes more than simply fullscreen itself |
2022-04-14 09:36:54 +0200 | <geekosaur> | so you could conceivably get "fake fullscreen" |
2022-04-14 09:37:48 +0200 | <Ether[m]> | i tried ", ("M-f", sendMessage $ Xmonad. Layout.MultiToggle Full) |
2022-04-14 09:38:15 +0200 | <Ether[m]> | s/.// |
2022-04-14 09:39:35 +0200 | <geekosaur> | (1) are yo using multitoggle? (2) its messages are all uppercase, last I checked |
2022-04-14 09:39:48 +0200 | <Ether[m]> | Yes |
2022-04-14 09:40:10 +0200 | <Ether[m]> | 2. Upper case for all? |
2022-04-14 09:40:13 +0200 | <geekosaur> | FULL |
2022-04-14 09:40:22 +0200 | <Ether[m]> | Oh yess |
2022-04-14 09:40:25 +0200 | <Ether[m]> | I did FULL |
2022-04-14 09:40:26 +0200 | <geekosaur> | https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Layout-MultiToggle-Instances… |
2022-04-14 09:40:31 +0200 | <Ether[m]> | No luck.. |
2022-04-14 09:43:25 +0200 | <geekosaur> | sendMessage $ Toggle FULL |
2022-04-14 09:45:17 +0200 | <Ether[m]> | Nope |
2022-04-14 09:45:39 +0200 | <Ether[m]> | 1) using multitoggle |
2022-04-14 09:46:58 +0200 | <Ether[m]> | 2) it works adding line to layout hook; $mkToggle (single FULL) |
2022-04-14 09:49:28 +0200 | <Ether[m]> | But in altercations dotfiles.. it allows me to use nav 2d to change focused window.. |
2022-04-14 09:49:37 +0200 | <Ether[m]> | Which is not working for me.. |
2022-04-14 09:52:10 +0200 | <geekosaur> | that is MultiToggle, right from its documentation |
2022-04-14 09:54:01 +0200 | <Ether[m]> | Nope, i figured it was navigation2d |
2022-04-14 09:54:15 +0200 | <Ether[m]> | I had to tell it what to do with FULL Layout |
2022-04-14 10:18:36 +0200 | coldpress_ | (~coldpress@72.136.212.35.bc.googleusercontent.com) |
2022-04-14 10:20:39 +0200 | haskl[error] | (~haskl@user/haskl) |
2022-04-14 10:22:34 +0200 | coldpress | (~coldpress@72.136.212.35.bc.googleusercontent.com) (Quit: ZNC 1.7.2 - https://znc.in) |
2022-04-14 10:22:34 +0200 | haskl | (~haskl@user/haskl) (Quit: Uh oh... ZNC disconnected.) |
2022-04-14 12:57:37 +0200 | theproffesor | (~theprofff@user/theproffesor) (Ping timeout: 260 seconds) |
2022-04-14 13:02:18 +0200 | theproffesor | (~theprofff@user/theproffesor) |
2022-04-14 14:07:42 +0200 | <abastro[m]> | geekosaur: I forgot how to debug a crash |
2022-04-14 14:07:46 +0200 | <abastro[m]> | How do i do it? |
2022-04-14 14:16:24 +0200 | cfricke | (~cfricke@user/cfricke) (Ping timeout: 248 seconds) |
2022-04-14 14:54:27 +0200 | benin | (~benin@183.82.204.110) (Ping timeout: 240 seconds) |
2022-04-14 15:03:36 +0200 | <geekosaur> | crash debugging is painful especially if it's in compiled code rather than FFI: debuggers realy want call stacks, but there isn't one in Haskell |
2022-04-14 15:06:42 +0200 | <geekosaur> | but you can compile with -g to get debug symbols which will help somewhat |
2022-04-14 15:07:48 +0200 | <geekosaur> | then you have to run your program in a debugger or attach to it from a debugger (the latter will be necessary if it's xmonad that is crashing; switch to a console vt and run gdb / lldb there) |
2022-04-14 15:10:27 +0200 | <geekosaur> | from there, you're on your own: I can help a bit if it's in the FFI but if it's in the RTS all I can do is point you to #ghc |
2022-04-14 15:31:25 +0200 | <geekosaur> | at some point I'll probably switch my default ghc to 9.2.2 and see if I replicate your crash locally, since I'm probably better at poking around with gdb than you are. but even so I may have to invoke #ghc if it'snot obviously FFI-related |
2022-04-14 15:31:35 +0200 | <geekosaur> | and/or will have to try to come up with a reproducer |
2022-04-14 15:54:30 +0200 | <abastro[m]> | Hmm |
2022-04-14 15:54:31 +0200 | <abastro[m]> | geekosaur: is there any way to see if the problem was caused by FFI portion? |
2022-04-14 15:55:21 +0200 | <geekosaur> | only by seeing if it has a call stack, since once you enter C there is one |
2022-04-14 15:55:32 +0200 | <geekosaur> | the STG is all jumps so there is no call stack |
2022-04-14 15:55:34 +0200 | <abastro[m]> | Or compiled code portion |
2022-04-14 15:55:35 +0200 | <abastro[m]> | I guess I need to compile with profiler to get proper exception messages |
2022-04-14 15:56:08 +0200 | <geekosaur> | are you getting messages? |
2022-04-14 15:56:23 +0200 | <geekosaur> | I thought you weren't, which suggested core dump |
2022-04-14 15:56:41 +0200 | <geekosaur> | sadly I'm about to be on a call, so won't be around much longer |
2022-04-14 15:59:10 +0200 | <geekosaur> | but yes,if you doget exception messages then you need to compile everything with --profile (stack) or -prof -prof-all (raw ghc / cabal) |
2022-04-14 16:08:39 +0200 | <abastro[m]> | Yep, I am not getting messages |
2022-04-14 16:08:46 +0200 | <abastro[m]> | So I guess core dump should be somewhere |
2022-04-14 16:08:48 +0200 | <abastro[m]> | I just wonder where it would be.. |
2022-04-14 16:14:11 +0200 | jao | (~jao@92.233.85.247) |
2022-04-14 17:07:11 +0200 | <geekosaur> | check ulimit |
2022-04-14 17:08:06 +0200 | <geekosaur> | most linuxes default to `ulimit -c 0` which disables core dumps. some (notably RHEL and possibly Fedora) feed it to a system daemon instead, but in that case you should get a popup (although if it's xmonad that's dumping core, that could work poorly) |
2022-04-14 17:16:32 +0200 | <geekosaur> | blegh, everything is happening today. counseling calls, service calls, … |
2022-04-14 17:20:34 +0200 | <abastro[m]> | Ohh. |
2022-04-14 17:25:40 +0200 | <geekosaur> | note that it's process-inherited, so if you change it in a terminal it won't affect anything already running |
2022-04-14 17:51:25 +0200 | <geekosaur> | aaaand we rebuild the whole world :) |
2022-04-14 17:51:40 +0200 | geekosaur | just set 9.2.2 as default and is rebuilding xmonad |
2022-04-14 17:57:05 +0200 | <geekosaur> | and then I'll have to do this again because I forgot -g |
2022-04-14 18:00:13 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
2022-04-14 18:00:30 +0200 | <Solid> | or because it won't crash ;) |
2022-04-14 18:00:41 +0200 | <geekosaur> | that remains to be seen |
2022-04-14 18:00:45 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
2022-04-14 18:01:00 +0200 | <geekosaur> | have to restart, then attach to it from a vt |
2022-04-14 18:01:19 +0200 | <geekosaur> | wonder if I need -prof too |
2022-04-14 18:01:28 +0200 | <geekosaur> | think I'll wait on that one |
2022-04-14 18:14:54 +0200 | edun | (~qbt@user/edun) |
2022-04-14 18:29:13 +0200 | benin | (~benin@183.82.204.110) |
2022-04-14 18:30:07 +0200 | edun | (~qbt@user/edun) (Quit: Leaving.) |
2022-04-14 18:30:33 +0200 | edun | (~qbt@user/edun) |
2022-04-14 18:32:23 +0200 | <geekosaur> | here goes nothing |
2022-04-14 18:32:43 +0200 | <geekosaur> | (now up in 9.2.2, will wait to see if it crashes before I do the gdb attach dance) |
2022-04-14 18:34:24 +0200 | edun | (~qbt@user/edun) (Client Quit) |
2022-04-14 18:35:17 +0200 | <geekosaur> | abastro[m], about how long does it take for crashes to happen? |
2022-04-14 18:35:26 +0200 | edun | (~qbt@user/edun) |
2022-04-14 18:36:06 +0200 | <geekosaur> | also one advantage of the xmonad under mate setup is I can recover from a crash |
2022-04-14 18:37:23 +0200 | <abastro[m]> | Well, it is unpredictable |
2022-04-14 18:37:31 +0200 | <abastro[m]> | Perhaps you could try reloading via mod+q, I guess |
2022-04-14 18:39:13 +0200 | edun | (~qbt@user/edun) (Client Quit) |
2022-04-14 18:39:35 +0200 | edun | (~qbt@user/edun) |
2022-04-14 18:50:22 +0200 | edun | (~qbt@user/edun) (Quit: Leaving.) |
2022-04-14 19:04:06 +0200 | Czernobog | (~Czernobog@user/czernobog) (Read error: Connection reset by peer) |
2022-04-14 19:04:56 +0200 | Czernobog | (~Czernobog@user/czernobog) |
2022-04-14 19:24:55 +0200 | steve__ | (~steve@ool-182c2b80.dyn.optonline.net) |
2022-04-14 19:26:30 +0200 | syg | (~syg@flamebot.net) |
2022-04-14 19:26:37 +0200 | redgloboli_ | (~redglobol@user/redgloboli) |
2022-04-14 19:27:56 +0200 | rieper|net | (~riepernet@sxbeta1.geo.uni-leipzig.de) |
2022-04-14 19:28:38 +0200 | globe_ | (~globe@stonebay32.com) |
2022-04-14 19:28:55 +0200 | scardina1 | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) |
2022-04-14 19:33:56 +0200 | theproffesor | (~theprofff@user/theproffesor) (*.net *.split) |
2022-04-14 19:33:56 +0200 | haskl[error] | (~haskl@user/haskl) (*.net *.split) |
2022-04-14 19:33:56 +0200 | rieper | (~riepernet@sxbeta1.geo.uni-leipzig.de) (*.net *.split) |
2022-04-14 19:33:56 +0200 | syg_ | (~syg@flamebot.net) (*.net *.split) |
2022-04-14 19:33:56 +0200 | steve_ | (~steve@ool-182c2b80.dyn.optonline.net) (*.net *.split) |
2022-04-14 19:33:57 +0200 | scardinal | (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (*.net *.split) |
2022-04-14 19:33:57 +0200 | deepy | (deepy@user/deepy) (*.net *.split) |
2022-04-14 19:33:57 +0200 | redgloboli | (~redglobol@user/redgloboli) (*.net *.split) |
2022-04-14 19:33:57 +0200 | Benzi-Junior | (~BenziJuni@dsl-149-64-179.hive.is) (*.net *.split) |
2022-04-14 19:33:57 +0200 | globe | (~globe@stonebay32.com) (*.net *.split) |
2022-04-14 19:37:15 +0200 | theproffesor | (~theprofff@user/theproffesor) |
2022-04-14 19:37:15 +0200 | haskl[error] | (~haskl@user/haskl) |
2022-04-14 19:37:15 +0200 | deepy | (deepy@user/deepy) |
2022-04-14 19:37:15 +0200 | Benzi-Junior | (~BenziJuni@dsl-149-64-179.hive.is) |
2022-04-14 20:41:15 +0200 | <geekosaur> | nice confusing boolean blindness in one of my own modules :( |
2022-04-14 20:41:22 +0200 | <geekosaur> | not even documented |
2022-04-14 20:57:42 +0200 | <geekosaur> | I think this is one of those modules I whipped up on the fly for someone and then minimally packaged. |
2022-04-14 20:58:10 +0200 | <geekosaur> | also, no crash yet |
2022-04-14 20:58:21 +0200 | <geekosaur> | abastro[m], can you put your config somewhere? |
2022-04-14 20:58:25 +0200 | <geekosaur> | @where paste |
2022-04-14 20:58:25 +0200 | <lambdabot> | Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com |
2022-04-14 21:29:43 +0200 | mohab | (~mohab@156.223.10.66) |
2022-04-14 21:30:22 +0200 | mohab | (~mohab@156.223.10.66) (Client Quit) |
2022-04-14 21:30:52 +0200 | mohab | (~mohab@156.223.10.66) |
2022-04-14 21:31:00 +0200 | mohab | (~mohab@156.223.10.66) (Client Quit) |
2022-04-14 23:43:37 +0200 | jao | (~jao@92.233.85.247) (Ping timeout: 256 seconds) |
2022-04-14 23:56:07 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b))) |
2022-04-14 23:56:07 +0200 | allbery_b | (~geekosaur@xmonad/geekosaur) |
2022-04-14 23:56:08 +0200 | allbery_b | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
2022-04-14 23:56:32 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |