#13707: xmobar crashes with segmentation faults? -------------------------------------+------------------------------------- Reporter: bgamari | Owner: (none) Type: bug | Status: new Priority: highest | Milestone: 8.2.1 Component: Compiler | Version: 8.2.1-rc2 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Type of failure: Compile-time | Unknown/Multiple crash or panic | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by andrewchen): You can reliably reproduce the crash by sending the xmobar window a lot of events, e.g. using xdotool to send a lot of mouse button presses, or as some members on github has pointed out, dragging other windows over the xmobar window, thus sending Expose events. You also need to have at least 1 monitor in your xmobarrc (e.g. have `Run Swap [] 10` in commands). The stack traces I got weren't very helpful, but most of them segfaulted on values read from the memory area used for return data from XNextEvent. Also see discussion here: https://ghc.haskell.org/trac/ghc/ticket/14346 -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/13707#comment:23 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler