I've just downgraded to 3.2.1-1 from testing, and it has the same
problem. I suppose that means that the problem is in a different
package. How should I go about finding it?
I've got the same problem on debian testing (awesome 3.2.1-1) right
after upgrading libxcb1 from 1.2-1 to 1.3-2.
Package: awesome
Version: 3.3-1
Severity: normal
I see something that looks like this too. I'm not able to recompile with
debugging symbols just now, but I do get this dump from glibc:
*** glibc detected *** awesome: free(): invalid pointer: 0x095007e8 ***
=== Backtrace: =
I've just downgraded to 3.2.1-1 from testing, and it has the same
problem. I suppose that means that the problem is in a different
package. How should I go about finding it?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
At 1244456525 time_t, Robert Norris wrote:
I see something that looks like this too. I'm not able to recompile with
debugging symbols just now, but I do get this dump from glibc:
This is #531310.
--
Julien Danjou
.''`. Debian Developer
: :' : http://julien.danjou.info
`. `'
On Sat, 6 Jun 2009 20:38:46 +0200
Julien Danjou a...@debian.org wrote:
At 1244310678 time_t, hizel wrote:
and with debug symbols
Adding more info would be nice if you can (like the previous bt).
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7822700 (LWP
At 1244224463 time_t, hizel wrote:
I'm recompile with debug symbol awesome. This is full back trace:
Does not looks like a coredump, rather than an assertion failure to me.
You do have a assert filed on stdout I guess.
And this should happen when you click on a wibox's widget, not starting
any
В Sat, 6 Jun 2009 11:58:17 +0200
Julien Danjou a...@debian.org пишет:
At 1244224463 time_t, hizel wrote:
I'm recompile with debug symbol awesome. This is full back trace:
Does not looks like a coredump, rather than an assertion failure to
me. You do have a assert filed on stdout I guess.
At 1244300328 time_t, hizel wrote:
run dpkg-buildpackage аnd start awesome in X:1
connected to it with gdb -p `pidof awesome`, continue
with start from the main menu awesome any program he coredump
and i'm ran full back trace command
So you click, and that's the click that make awesome
В Sat, 6 Jun 2009 18:37:31 +0200
Julien Danjou a...@debian.org пишет:
At 1244300328 time_t, hizel wrote:
run dpkg-buildpackage аnd start awesome in X:1
connected to it with gdb -p `pidof awesome`, continue
with start from the main menu awesome any program he coredump
and i'm ran full
В Sat, 6 Jun 2009 21:42:59 +0400
hizel hi...@vyborg.ru пишет:
В Sat, 6 Jun 2009 18:37:31 +0200
Julien Danjou a...@debian.org пишет:
At 1244300328 time_t, hizel wrote:
run dpkg-buildpackage аnd start awesome in X:1
connected to it with gdb -p `pidof awesome`, continue
with start
At 1244310678 time_t, hizel wrote:
and with debug symbols
Adding more info would be nice if you can (like the previous bt).
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7822700 (LWP 7699)]
0x08054702 in client_seturgent ()
(gdb) bt
#0 0x08054702 in
Package: awesome
Version: 3.3-1
Severity: normal
I'm recompile with debug symbol awesome. This is full back trace:
#0 0xb7ff6424 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7a7b680 in raise () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#2 0xb7a7ed68 in
12 matches
Mail list logo
