threading bug?

[Kip Macy]

That doesn't look like the actual problem. Can you
send the output of "thread apply all bt", (assuming
they actually incorporated my patch for looking at
all the threads in the core).

			-Kip

On Sun, 21 Sep 2003, Jeroen Ruigrok/asmodai wrote:

> I was trying Opera today and noticed how it was way more unstable (just
> upgraded my box to the latest sources of today).
>
> A traceback of one of the coredumps yields:
>
> (gdb) bt
> #0  0x289c1b0d in _atomic_lock () from /usr/lib/libc_r.so.4
> #1  0x289c1ad6 in _spinlock_debug (lck=0xd0d0d100,
>     fname=0x28a03e80 "/usr/src/lib/libc_r/uthread/uthread_mutex.c", lineno=446)
>     at /usr/src/lib/libc_r/uthread/uthread_spinlock.c:104
> #2  0x289c5a76 in _pthread_mutex_lock (mutex=0xaa52db4)
>     at /usr/src/lib/libc_r/uthread/uthread_mutex.c:446
> #3  0x838d669 in XAllocColor ()
> #4  0x8388a3a in XAllocColor ()
> #5  0x8388969 in XAllocColor ()
> #6  0x2898a2c3 in _thread_start ()
>     at /usr/src/lib/libc_r/uthread/uthread_create.c:323
> #7  0x0 in ?? ()
>
> Notice the d0d0 in lck at frame #1.  I run with malloc.conf -> AJ.
>
> Did we recently change something in the threading department that could
> cause this?
>
> --
> Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
> PGP fingerprint: 2D92 980E 45FE 2C28 9DB7  9D88 97E6 839B 2EAC 625B
> http://www.tendra.org/   | http://www.in-nomine.org/~asmodai/diary/
> Don't try to find the Answer where there ain't no Question here...
>