Subject: Re: After newlock2 merge: Different pthread behavior foruserlandprograms?
To: Matthias Drochner <M.Drochner@fz-juelich.de>
From: Andrew Doran <ad@NetBSD.org>
Date: 03/24/2007 03:03:09
On Sat, Mar 24, 2007 at 12:45:54AM +0100, Matthias Drochner wrote:
> M.Drochner@fz-juelich.de said:
> > Sometimes a part of the xfce4 desktop dies.
> Fwiw, I'm just noticing that there are 2 new coredumps
> in my home dir, from xfce4-panel and xfce-mcs-manager.
> The stacktrace looks identical for both:
> #0 0xbb3110ff in kill () from /usr/lib/libc.so.12
> #1 0xbb3d8097 in pthread__assertfunc () from /usr/lib/libpthread.so.0
> #2 0xbb3d6e4c in pthread_spinlock () from /usr/lib/libpthread.so.0
> #3 0xbb3d8edd in pthread_exit () from /usr/lib/libpthread.so.0
> #4 0xbb3d67f8 in poll () from /usr/lib/libpthread.so.0
> #5 0xbb40ecaf in g_main_context_check () from /usr/pkg/lib/libglib-2.0.so.0
> #6 0xbb40f077 in g_main_loop_run () from /usr/pkg/lib/libglib-2.0.so.0
> #7 0xbb996831 in gtk_main () from /usr/pkg/lib/libgtk-x11-2.0.so.0
> #8 0x0804a9e3 in main ()
> Whatever the error is, it is not one of those catching application
> misbehaviour. Rather some libpthread internal thing.
> And I wasn't running setiathome at this time, so my statement
> "everything is fine as long as the CPUs are busy" still holds.
I've seen a similar trace recently from a FUSE app (pthread_spinlock), I'll
have look in the next few days. Apparently it's not hard to reproduce the
WRT to the instability you're seeing.. I've been running -current on my
desktop and main development machine for quite a while and have not seen
any problems like that. I did have issues a while back with xfce 4.4 from
pkgsrc-wip (similar to what you mention) but have not seen then with
any other apps.