Logs: liberachat/#xmonad
| 2022-04-14 06:29:09 | <Solid> | use the git version in the meantime :) |
| 2022-04-14 06:29:33 | <abastro[m]> | Yep |
| 2022-04-14 06:29:51 | <abastro[m]> | Anyway that is more or less trivial probelm |
| 2022-04-14 06:30:16 | × | m5zs7k quits (aquares@web10.mydevil.net) (Ping timeout: 248 seconds) |
| 2022-04-14 06:30:19 | <abastro[m]> | Bigger one was with unidentifiable xmonad random crash, it doesn't even reproduce reliably |
| 2022-04-14 06:30:23 | <abastro[m]> | It's just random |
| 2022-04-14 06:30:25 | <abastro[m]> | Meh |
| 2022-04-14 06:30:51 | → | m5zs7k joins (aquares@web10.mydevil.net) |
| 2022-04-14 06:34:32 | → | cfricke joins (~cfricke@user/cfricke) |
| 2022-04-14 07:19:28 | × | smashgra_ quits (~smashgrab@bare.metal.computer) (Quit: ZNC 1.7.2+deb3 - https://znc.in) |
| 2022-04-14 07:19:46 | → | smashgrab joins (~smashgrab@bare.metal.computer) |
| 2022-04-14 07:33:32 | <geekosaur> | Solid, Hackage trustees can only do version bounds changes in the cabal file, not actual package changes |
| 2022-04-14 07:35:01 | <Solid> | oh I see |
| 2022-04-14 07:36:10 | <Ether[m]> | I dont why but it seems XMonad.Layout.Fullscreen does have a way to add a binding.. |
| 2022-04-14 07:36:43 | <geekosaur> | because it's up to the app, which often dpoes more than simply fullscreen itself |
| 2022-04-14 07:36:54 | <geekosaur> | so you could conceivably get "fake fullscreen" |
| 2022-04-14 07:37:48 | <Ether[m]> | i tried ", ("M-f", sendMessage $ Xmonad. Layout.MultiToggle Full) |
| 2022-04-14 07:38:15 | <Ether[m]> | s/.// |
| 2022-04-14 07:39:35 | <geekosaur> | (1) are yo using multitoggle? (2) its messages are all uppercase, last I checked |
| 2022-04-14 07:39:48 | <Ether[m]> | Yes |
| 2022-04-14 07:40:10 | <Ether[m]> | 2. Upper case for all? |
| 2022-04-14 07:40:13 | <geekosaur> | FULL |
| 2022-04-14 07:40:22 | <Ether[m]> | Oh yess |
| 2022-04-14 07:40:25 | <Ether[m]> | I did FULL |
| 2022-04-14 07:40:26 | <geekosaur> | https://hackage.haskell.org/package/xmonad-contrib-0.17.0/docs/XMonad-Layout-MultiToggle-Instances.html#t:StdTransformers |
| 2022-04-14 07:40:31 | <Ether[m]> | No luck.. |
| 2022-04-14 07:43:25 | <geekosaur> | sendMessage $ Toggle FULL |
| 2022-04-14 07:45:17 | <Ether[m]> | Nope |
| 2022-04-14 07:45:39 | <Ether[m]> | 1) using multitoggle |
| 2022-04-14 07:46:58 | <Ether[m]> | 2) it works adding line to layout hook; $mkToggle (single FULL) |
| 2022-04-14 07:49:28 | <Ether[m]> | But in altercations dotfiles.. it allows me to use nav 2d to change focused window.. |
| 2022-04-14 07:49:37 | <Ether[m]> | Which is not working for me.. |
| 2022-04-14 07:52:10 | <geekosaur> | that is MultiToggle, right from its documentation |
| 2022-04-14 07:54:01 | <Ether[m]> | Nope, i figured it was navigation2d |
| 2022-04-14 07:54:15 | <Ether[m]> | I had to tell it what to do with FULL Layout |
| 2022-04-14 08:18:36 | → | coldpress_ joins (~coldpress@72.136.212.35.bc.googleusercontent.com) |
| 2022-04-14 08:20:39 | → | haskl[error] joins (~haskl@user/haskl) |
| 2022-04-14 08:22:34 | × | coldpress quits (~coldpress@72.136.212.35.bc.googleusercontent.com) (Quit: ZNC 1.7.2 - https://znc.in) |
| 2022-04-14 08:22:34 | × | haskl quits (~haskl@user/haskl) (Quit: Uh oh... ZNC disconnected.) |
| 2022-04-14 10:57:37 | × | theproffesor quits (~theprofff@user/theproffesor) (Ping timeout: 260 seconds) |
| 2022-04-14 11:02:18 | → | theproffesor joins (~theprofff@user/theproffesor) |
| 2022-04-14 12:07:42 | <abastro[m]> | geekosaur: I forgot how to debug a crash |
| 2022-04-14 12:07:46 | <abastro[m]> | How do i do it? |
| 2022-04-14 12:16:24 | × | cfricke quits (~cfricke@user/cfricke) (Ping timeout: 248 seconds) |
| 2022-04-14 12:54:27 | × | benin quits (~benin@183.82.204.110) (Ping timeout: 240 seconds) |
| 2022-04-14 13:03:36 | <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 13:06:42 | <geekosaur> | but you can compile with -g to get debug symbols which will help somewhat |
| 2022-04-14 13:07:48 | <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 13:10:27 | <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 13:31:25 | <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 13:31:35 | <geekosaur> | and/or will have to try to come up with a reproducer |
| 2022-04-14 13:54:30 | <abastro[m]> | Hmm |
| 2022-04-14 13:54:31 | <abastro[m]> | geekosaur: is there any way to see if the problem was caused by FFI portion? |
| 2022-04-14 13:55:21 | <geekosaur> | only by seeing if it has a call stack, since once you enter C there is one |
| 2022-04-14 13:55:32 | <geekosaur> | the STG is all jumps so there is no call stack |
| 2022-04-14 13:55:34 | <abastro[m]> | Or compiled code portion |
| 2022-04-14 13:55:35 | <abastro[m]> | I guess I need to compile with profiler to get proper exception messages |
| 2022-04-14 13:56:08 | <geekosaur> | are you getting messages? |
| 2022-04-14 13:56:23 | <geekosaur> | I thought you weren't, which suggested core dump |
| 2022-04-14 13:56:41 | <geekosaur> | sadly I'm about to be on a call, so won't be around much longer |
| 2022-04-14 13:59:10 | <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 14:08:39 | <abastro[m]> | Yep, I am not getting messages |
| 2022-04-14 14:08:46 | <abastro[m]> | So I guess core dump should be somewhere |
| 2022-04-14 14:08:48 | <abastro[m]> | I just wonder where it would be.. |
| 2022-04-14 14:14:11 | → | jao joins (~jao@92.233.85.247) |
| 2022-04-14 15:07:11 | <geekosaur> | check ulimit |
| 2022-04-14 15:08:06 | <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 15:16:32 | <geekosaur> | blegh, everything is happening today. counseling calls, service calls, … |
| 2022-04-14 15:20:34 | <abastro[m]> | Ohh. |
| 2022-04-14 15:25:40 | <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 15:51:25 | <geekosaur> | aaaand we rebuild the whole world :) |
| 2022-04-14 15:51:40 | geekosaur | just set 9.2.2 as default and is rebuilding xmonad |
| 2022-04-14 15:57:05 | <geekosaur> | and then I'll have to do this again because I forgot -g |
| 2022-04-14 16:00:13 | × | liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-04-14 16:00:30 | <Solid> | or because it won't crash ;) |
| 2022-04-14 16:00:41 | <geekosaur> | that remains to be seen |
| 2022-04-14 16:00:45 | → | liskin[m] joins (~liskinmat@2001:470:69fc:105::768) |
| 2022-04-14 16:01:00 | <geekosaur> | have to restart, then attach to it from a vt |
| 2022-04-14 16:01:19 | <geekosaur> | wonder if I need -prof too |
| 2022-04-14 16:01:28 | <geekosaur> | think I'll wait on that one |
| 2022-04-14 16:14:54 | → | edun joins (~qbt@user/edun) |
| 2022-04-14 16:29:13 | → | benin joins (~benin@183.82.204.110) |
| 2022-04-14 16:30:07 | × | edun quits (~qbt@user/edun) (Quit: Leaving.) |
| 2022-04-14 16:30:33 | → | edun joins (~qbt@user/edun) |
| 2022-04-14 16:32:23 | <geekosaur> | here goes nothing |
| 2022-04-14 16:32:43 | <geekosaur> | (now up in 9.2.2, will wait to see if it crashes before I do the gdb attach dance) |
| 2022-04-14 16:34:24 | × | edun quits (~qbt@user/edun) (Client Quit) |
| 2022-04-14 16:35:17 | <geekosaur> | abastro[m], about how long does it take for crashes to happen? |
| 2022-04-14 16:35:26 | → | edun joins (~qbt@user/edun) |
| 2022-04-14 16:36:06 | <geekosaur> | also one advantage of the xmonad under mate setup is I can recover from a crash |
| 2022-04-14 16:37:23 | <abastro[m]> | Well, it is unpredictable |
| 2022-04-14 16:37:31 | <abastro[m]> | Perhaps you could try reloading via mod+q, I guess |
| 2022-04-14 16:39:13 | × | edun quits (~qbt@user/edun) (Client Quit) |
| 2022-04-14 16:39:35 | → | edun joins (~qbt@user/edun) |
| 2022-04-14 16:50:22 | × | edun quits (~qbt@user/edun) (Quit: Leaving.) |
| 2022-04-14 17:04:06 | × | Czernobog quits (~Czernobog@user/czernobog) (Read error: Connection reset by peer) |
| 2022-04-14 17:04:56 | → | Czernobog joins (~Czernobog@user/czernobog) |
| 2022-04-14 17:24:55 | → | steve__ joins (~steve@ool-182c2b80.dyn.optonline.net) |
| 2022-04-14 17:26:30 | → | syg joins (~syg@flamebot.net) |
| 2022-04-14 17:26:37 | → | redgloboli_ joins (~redglobol@user/redgloboli) |
All times are in UTC.