crashes on latest xmonad
Hi all, I'm experiencing crashes on the latest xmonad. This is on a x86-64 computer, so that may be related. The error message I get is: /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "droundy" /etc/gdm/Xsession: Beginning session setup... 4 /bin/sh: dmenu_path: command not found 4 /bin/sh: dmenu_path: command not found kbuildsycoca running... 4 /bin/sh: dmenu_path: command not found /bin/sh: dmenu_path: command not found /bin/sh: dmenu_path: command not found Failed to retrieve terminal server from activation server xmonad: internal error: ARR_WORDS object entered! (GHC version 6.6 for x86_64_unknown_linux) Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug This doesn't look good. Any suggestions? Is it really a ghc bug? Alas, since ion3 is also broken, I'm reduced to using gnome. On the plus side, my productivity on grant writing might actually benefit, since I'll have more trouble working on multiple projects simultaneously... -- David Roundy Department of Physics Oregon State University
droundy:
Hi all,
I'm experiencing crashes on the latest xmonad. This is on a x86-64 computer, so that may be related. The error message I get is:
/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "droundy" /etc/gdm/Xsession: Beginning session setup... 4 /bin/sh: dmenu_path: command not found 4 /bin/sh: dmenu_path: command not found kbuildsycoca running... 4 /bin/sh: dmenu_path: command not found /bin/sh: dmenu_path: command not found /bin/sh: dmenu_path: command not found Failed to retrieve terminal server from activation server xmonad: internal error: ARR_WORDS object entered! (GHC version 6.6 for x86_64_unknown_linux) Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug
This doesn't look good. Any suggestions? Is it really a ghc bug?
Can you try recompiling with -O or -Onot, and with -fvia-C. We'll find out if its a GHC code gen bug (almost certainly a ghc bug). -- Don
On Fri, May 25, 2007 at 02:21:16AM +1000, Donald Bruce Stewart wrote:
This doesn't look good. Any suggestions? Is it really a ghc bug?
Can you try recompiling with -O or -Onot, and with -fvia-C. We'll find out if its a GHC code gen bug (almost certainly a ghc bug).
Any hints how to do this? I'm a cabal-illiterate... and I almost certainly won't have a chance to try this until tomorrow. -- David Roundy Department of Physics Oregon State University
droundy:
On Fri, May 25, 2007 at 02:21:16AM +1000, Donald Bruce Stewart wrote:
This doesn't look good. Any suggestions? Is it really a ghc bug?
Can you try recompiling with -O or -Onot, and with -fvia-C. We'll find out if its a GHC code gen bug (almost certainly a ghc bug).
Any hints how to do this? I'm a cabal-illiterate... and I almost certainly won't have a chance to try this until tomorrow.
Oh, experiment with some different settings in xmonad.cabal: ghc-options: -funbox-strict-fields -O2 -fasm -Wall -optl-Wl,-s Try -O, -O -fvia-c, -Onot and such. See if we can narrow it down for Simon et al. -- Don
On Fri, May 25, 2007 at 02:39:17AM +1000, Donald Bruce Stewart wrote:
droundy:
On Fri, May 25, 2007 at 02:21:16AM +1000, Donald Bruce Stewart wrote:
This doesn't look good. Any suggestions? Is it really a ghc bug?
Can you try recompiling with -O or -Onot, and with -fvia-C. We'll find out if its a GHC code gen bug (almost certainly a ghc bug).
Any hints how to do this? I'm a cabal-illiterate... and I almost certainly won't have a chance to try this until tomorrow.
Oh, experiment with some different settings in xmonad.cabal:
ghc-options: -funbox-strict-fields -O2 -fasm -Wall -optl-Wl,-s
Try -O, -O -fvia-c, -Onot and such. See if we can narrow it down for Simon et al.
Hmmm. Now the problem has disappeared (on recompiling). Darn, a heisenbug. Oh well, I'll try this again if the problem ever crops up again. -- David Roundy Department of Physics Oregon State University
droundy:
On Fri, May 25, 2007 at 02:39:17AM +1000, Donald Bruce Stewart wrote:
droundy:
On Fri, May 25, 2007 at 02:21:16AM +1000, Donald Bruce Stewart wrote:
This doesn't look good. Any suggestions? Is it really a ghc bug?
Can you try recompiling with -O or -Onot, and with -fvia-C. We'll find out if its a GHC code gen bug (almost certainly a ghc bug).
Any hints how to do this? I'm a cabal-illiterate... and I almost certainly won't have a chance to try this until tomorrow.
Oh, experiment with some different settings in xmonad.cabal:
ghc-options: -funbox-strict-fields -O2 -fasm -Wall -optl-Wl,-s
Try -O, -O -fvia-c, -Onot and such. See if we can narrow it down for Simon et al.
Hmmm. Now the problem has disappeared (on recompiling). Darn, a heisenbug. Oh well, I'll try this again if the problem ever crops up again.
Maybe a cosmic ray corrupted your last compile :-) Anyway -- good! This means , I think, there are no open bugs preventing 0.2. We're now entering a few days of feature freeze to the core, and a process of doc writing and QC testing. -- Don
participants (2)
-
David Roundy -
dons＠cse.unsw.edu.au