This is probably a pretty awful bug report, but I was wondering if
anyone else was encountering periodic segfaults with Awesome? I can't
find any particular cause, it just happens occasionally
I don't have awesome compiled with debug flags, so this is the best
stack trace I can do:
Continuing.
Continuing.
process 5701 is executing new program: /bin/zsh
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
process 5701 is executing new program: /usr/bin/awesome
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Traceback (most recent call last):
File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3200.4-gdb.py",
line 9, in <module>
from gobject import register
File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
import gdb.backtrace
ImportError: No module named backtrace
Program received signal SIGSEGV, Segmentation fault.
0x00007f4ade78ab50 in __memcpy_ssse3 () from /lib/libc.so.6
Continuing.
[Inferior 1 (process 5701) exited with code 01]
Starting program: /usr/bin/awesome startx
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[Inferior 1 (process 1778) exited with code 01]
--
I just got this out of gdb -p $(pgrep awesome)
Does this look familiar to anyone? Is there anything I can do to
narrow down the problem?
ellie
--
To unsubscribe, send mail to [email protected].
