At 1242331287 time_t, Uli Schlachter wrote:
And another backtrace, this time with gdb...
The plan for is to finally use -O0 -fno-inline and see what happens. (btw
yay,
finally done with school and I got time for this!) (Oh and another btw: I
still
don't know any way to reproduce this, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Julien Danjou wrote:
At 1242331287 time_t, Uli Schlachter wrote:
And another backtrace, this time with gdb...
The plan for is to finally use -O0 -fno-inline and see what happens. (btw
yay,
finally done with school and I got time for this!) (Oh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nikos Ntarmos wrote:
Hi there.
FWIW I've also been experiencing segfaults on FreeBSD/i386, however only
when X goes down before awesome. A short look into this revealed it was
due to widgets update hooks being scheduled for some time after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Uli Schlachter wrote:
Uli Schlachter wrote:
Julien Danjou wrote:
At 1241874772 time_t, Uli Schlachter wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Uli Schlachter wrote:
Julien Danjou wrote:
At 1241874772 time_t, Uli Schlachter wrote:
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).
Hi there.
FWIW I've also been experiencing segfaults on FreeBSD/i386, however only
when X goes down before awesome. A short look into this revealed it was
due to widgets update hooks being scheduled for some time after
awesome and X is down. I never got around to looking into this any
further but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Julien Danjou wrote:
At 1241874772 time_t, Uli Schlachter wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
no idea what exactly just happened, but awesome crashed when I pressed ctrl-q in
konqueror. Syslog says:
May 9 10:49:21 psytux kernel: [ 8809.790642] awesome[4487]: segfault at 257a000
ip 0032a5c7d511 sp 7fffbd55e868 error 4 in
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
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
At 1241874772 time_t, Uli Schlachter wrote:
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? :(
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...
-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
At 1241876690 time_t, Uli Schlachter wrote:
jd: I guess the debian version doesn't have this... bug?
Should not.
--
Julien Danjou
// ᐰ jul...@danjou.info http://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
// My root password is
signature.asc
Description:
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
Shouldn't you get it reverted if it's a bad commit?
--
To unsubscribe,
Maarten Maathuis pisze:
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
Shouldn't you get it reverted if it's a bad
16 matches
Mail list logo