Date: Wed, 21 Apr 2004 09:18:39 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Joe Marcus Clarke <marcus@FreeBSD.org> Cc: freebsd-hackers@FreeBSD.org Subject: Re: Help: threading problem in non-threaded applications Message-ID: <Pine.GSO.4.10.10404210916330.1169-100000@pcnet5.pcnet.com> In-Reply-To: <1082524938.41182.26.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 21 Apr 2004, Joe Marcus Clarke wrote: > On Tue, 2004-04-20 at 17:08, Daniel Eischen wrote: > > On Tue, 20 Apr 2004, Joe Marcus Clarke wrote: > > > > > I have a problem I'm hoping someone can help me with. GTK+ 2.4 > > > introduced a new file selection GUI which works just fine in threaded > > > and non-threaded applications. However, GNOME 2.6 augmented this dialog > > > with a dynamically loadable threaded shared object. The GNOME version > > > is automatically used by all GTK+ apps when run under a GNOME desktop if > > > libgnomeui is installed. > > > > Shared libraries shouldn't link with threading libraries > > unless they actually create threads behind the scenes. > > Actually, even so, they could force the (unthreaded) > > applications that link with them to explicitly supply > > the thread library in the link option. > > And that's the case here. The underlying libraries are creating and > using threads. But what happens when a non-threaded application loads a > thread library via dlopen() (which is the case here)? Here's the stack > trace I see: In that case you're going to have to link the application to a threads library. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10404210916330.1169-100000>