Adam Nielsen <[email protected]> writes:
>> I verified that indeed X does not crash. It's awesome which crashes and
>> then X just exits. Perhaps someone knowledgeable could have a look at
>> the attached backtrace? What I did is running
>
> Unfortunately the backtrace isn't really informative enough. You will
> probably need to compile Awesome with debugging information enabled, then run
> it through GDB.
Okay, I compiled awesome 3.4.4 from Debian with debug symobls using
DEB_BUILD_OPTIONS="nostrip noopt" fakeroot apt-get -b source awesome
This should build with -O0, but still the backtrace says "value
optimized away". How to solve this?
> You can do this by running startx in one terminal, and tell it to load
> xterm or something, then in another terminal run "export DISPLAY=:0.0"
> then "gdb awesome" and "run" it. Switching back to X should show
> Awesome running. When it crashes X will no longer exit but it may
> lock up, you should switch back to the terminal/console running gdb
> and get a backtrace from there. This should give the exact line of
> code where the crash occurs.
I did that, this is the log of the session
(gdb) run
Starting program: /usr/bin/awesome
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
malloc_consolidate (av=0x7ffff3ad7e60) at malloc.c:5111
5111 malloc.c: No such file or directory.
in malloc.c
(gdb) bt
#0 malloc_consolidate (av=0x7ffff3ad7e60) at malloc.c:5111
#1 0x00007ffff37fa668 in _int_free (av=0x7ffff3ad7e60, p=0x88a500) at
malloc.c:4990
#2 0x00007ffff37fd9bc in *__GI___libc_free (mem=<value optimized out>) at
malloc.c:3738
#3 0x00007ffff43da355 in ?? () from /usr/lib/liblua5.1.so.0
#4 0x00007ffff43d2321 in ?? () from /usr/lib/liblua5.1.so.0
#5 0x00007ffff43d63bf in ?? () from /usr/lib/liblua5.1.so.0
#6 0x00007ffff43d05ab in ?? () from /usr/lib/liblua5.1.so.0
#7 0x00007ffff43d0648 in ?? () from /usr/lib/liblua5.1.so.0
#8 0x00007ffff43d59cf in ?? () from /usr/lib/liblua5.1.so.0
#9 0x000000000040fb96 in awesome_atexit () at
/home/cwg/pkg/awesome-3.4.4/awesome.c:96
#10 0x000000000040fbf9 in awesome_restart () at
/home/cwg/pkg/awesome-3.4.4/awesome.c:276
#11 0x000000000041b9da in event_handle_configurenotify (data=<value optimized
out>, connection=0x669d40, ev=0x8e4a10)
at /home/cwg/pkg/awesome-3.4.4/event.c:314
#12 0x000000000040f59d in a_xcb_check_cb (loop=<value optimized out>, w=<value
optimized out>, revents=<value optimized out>)
at /home/cwg/pkg/awesome-3.4.4/awesome.c:223
#13 0x00007ffff45f0481 in ev_invoke_pending () from /usr/lib/libev.so.3
#14 0x00007ffff45f51bc in ev_loop () from /usr/lib/libev.so.3
#15 0x0000000000410526 in main (argc=<value optimized out>, argv=<value
optimized out>) at /home/cwg/pkg/awesome-3.4.4/awesome.c:572
> In the mean time, you can replace the line that runs Awesome with something
> like "while true; do awesome; done", then instead of everything crashing now
> and then, all your windows will flicker occasionally when Awesome crashes and
> is immediately reloaded.
Thank you very much for your kind help.
Christoph
--
To unsubscribe, send mail to [email protected].
