You are not logged in.
Pages: 1
Hello,
Recently I've been unable to start xmonad, getting segfaults:
> xmonad
[1] 23374 segmentation fault (core dumped) xmonadUnfortunately running this via gdb doesn't provide much info
> gdb xmonad
GNU gdb (GDB) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from xmonad...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/xmonad
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
process 23523 is executing new program: /home/przemek/git-work/gitlab/xmonad/xmonad-x86_64-linux
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) where
#0 0x0000000000000000 in ?? ()
#1 0x00000000004044dd in _init ()
#2 0x0000000000000000 in ?? ()
(gdb) Any idea what might be the issue? I haven't researched the problem much because of lack of time, but maybe someone encountered something similar recently and has a solution? ![]()
P.
Offline
Pages: 1