Uli Schlachter pisze: > Julien Danjou wrote: >> At 1241861577 time_t, Uli Schlachter wrote: >>> I have no idea what caused this and it doesn't seem reproducible which is >>> why I >>> won't open a bug report. I'm updating to rc2 now and I will run awesome in >>> valgrind. Let's see if I can find anything... >> What I can suggest is to call ulimit -c unlimited before running awesome. >> At least you'll have a coredump. >> And if you can reproduce it, recompiling with -O0 -fno-inline can help >> to have a more complete bt. > >> Cheers, > > Well, I went with valgrind and now got this backtrace (man, I miss debugging > symbols... btw I still can't compile awesome due to some missing > dependencies). > Anyone got some ideas what's going on? Proposals how to get my beloved debug > symbols? :( Hi, Do you have git version of xcb-proto ? If yes revert commit fe7b12db4fc0e95f3eef038581bf2154e1727c7a, "Correct the length calculation for the value field of GetPropertyReply." ... and rebuild libxcb and xcb-util ... :p
Mariusz Ceier -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
