-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Mariusz Ceier wrote:
> 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
>
Nope, this debian testing + awesome 3.3* from unstable (which pulled in
libxcb-atom1, libxcb-keysyms1 and libxdg-basedir1 from unstable).
jd: I guess the debian version doesn't have this... "bug"?
- --
"Do you know that books smell like nutmeg or some spice from a foreign land?"
-- Faber in Fahrenheit 451
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQEcBAEBCAAGBQJKBYjPAAoJECLkKOvLj8sG7PsIAIcCwC5mHNZcpTT+K4amAWVI
AfWqK9uWonDcB6ZRJlm19cCoTNb7x56aXXZzyUJwbDxDPhEk7e8UbtTEIGVuZ2JU
ObfZczyEmgdIe522nxLpYemSlX8USZLPqSGaxpfCF032CVfSFB7Ezgh7gav/gfZb
ijuq+xNf1qChjFJom1QuThMTuLnd8px+fcUEEAqOMu7UpH97AAAlKGJjaw4BAh+p
889QO+lSMyf1Tm1cRSWwC04yOeI7Iil525AagLMLAMpwqnrEQ+8DQ7NPVVXqMo7H
hrJvgQoQS+XXNT5d3iXkJoKIA2qdj5tcq8ZOln21eb9g5j777ci8xWztnxRDsmE=
=G88D
-----END PGP SIGNATURE-----
--
To unsubscribe, send mail to [email protected].
