Greets,
On Sun 08 May 2011 16:34, l...@gnu.org (Ludovic Courtès) writes:
> writes:
>
>> Recent changes to stable-2.0 seem to cause a deadlock in scwm. Here is the
>> last 10 frames of a backtrace.
These are fixed.
> I’m not sure if this is related
It's not :)
> but there’s this new error t
Andy Wingo wrote:
> On Sat 07 May 2011 16:58, writes:
>
> > Recent changes to stable-2.0 seem to cause a deadlock in scwm. Here
> > is the last 10 frames of a backtrace.
>
> Fixed. Apologies for the long delay.
np! Great Thankfulness is applied.
-Dale
On Sat 07 May 2011 16:58, writes:
> Recent changes to stable-2.0 seem to cause a deadlock in scwm. Here
> is the last 10 frames of a backtrace.
Fixed. Apologies for the long delay.
Regards,
Andy
--
http://wingolog.org/
dsm...@roadrunner.com wrote:
>
> "Ludovic Courtès" wrote:
> > Hi,
> >
> > writes:
> >
> > > Recent changes to stable-2.0 seem to cause a deadlock in scwm. Here is
> > > the last 10 frames of a backtrace.
> >
> > I’m not sure if this is related but there’s this new error that ha
"Ludovic Courtès" wrote:
> Hi,
>
> writes:
>
> > Recent changes to stable-2.0 seem to cause a deadlock in scwm. Here is the
> > last 10 frames of a backtrace.
>
> I’m not sure if this is related but there’s this new error that has
> started happening from time to time:
>
[ removed ]
Hi,
writes:
> Recent changes to stable-2.0 seem to cause a deadlock in scwm. Here is the
> last 10 frames of a backtrace.
I’m not sure if this is related but there’s this new error that has
started happening from time to time:
--8<---cut here---start->8---
Recent changes to stable-2.0 seem to cause a deadlock in scwm. Here is the
last 10 frames of a backtrace.
-Dale
(gdb) bt
#0 0xb77fa424 in __kernel_vsyscall ()
#1 0xb734cf02 in __lll_lock_wait ()
at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:142
#2 0xb734839b in _L_l
