From owner-freebsd-threads@FreeBSD.ORG Mon Sep 1 11:02:09 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C191816A4C2 for ; Mon, 1 Sep 2003 11:02:09 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA7B344015 for ; Mon, 1 Sep 2003 11:01:37 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h81I1bUp002623 for ; Mon, 1 Sep 2003 11:01:37 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h81I1bXm002617 for freebsd-threads@freebsd.org; Mon, 1 Sep 2003 11:01:37 -0700 (PDT) Date: Mon, 1 Sep 2003 11:01:37 -0700 (PDT) Message-Id: <200309011801.h81I1bXm002617@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2003 18:02:10 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/06/13] kern/19247 threads uthread_sigaction.c does not do anything o [2002/01/16] kern/33951 threads pthread_cancel is ignored 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/01/19] bin/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVT o [2001/01/25] bin/24632 threads libc_r delicate deviation from libc in ha o [2001/04/02] bin/26307 threads libc_r aborts when using the KDE media pl o [2001/10/31] bin/31661 threads pthread_kill signal handler doesn't get s o [2001/11/26] bin/32295 threads pthread dont dequeue signals o [2002/03/07] bin/35622 threads sigaltstack is missing in libc_r o [2002/06/27] bin/39922 threads [PATCH?] Threaded applications executed w o [2003/03/02] bin/48856 threads Setting SIGCHLD to SIG_IGN still leaves z o [2003/03/10] bin/49087 threads Signals lost in programs linked with libc a [2003/04/08] bin/50733 threads buildworld won't build, because of linkin o [2003/05/07] bin/51949 threads thread in accept cannot be cancelled o [2002/02/01] i386/34536 threads accept() blocks other threads o [2000/07/18] kern/20016 threads pthreads: Cannot set scheduling timer/Can o [2002/05/25] kern/38549 threads the procces compiled whith pthread stoppe o [2002/10/10] kern/43887 threads abnormal CPU useage when use pthread_mute o [2003/05/30] kern/52817 threads top(1) shows garbage for threaded process o [2000/08/26] misc/20861 threads libc_r does not honor socket timeouts o [2001/01/25] misc/24641 threads pthread_rwlock_rdlock can deadlock o [2002/08/04] misc/41331 threads Pthread library open sets O_NONBLOCK flag 19 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/09/09] bin/30464 threads pthread mutex attributes -- pshared o [2002/05/02] bin/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwri o [2000/05/25] misc/18824 threads gethostbyname is not thread safe o [2000/10/21] misc/22190 threads A threaded read(2) from a socketpair(2) f o [2002/07/16] misc/40671 threads pthread_cancel doesn't remove thread from 5 problems total. From owner-freebsd-threads@FreeBSD.ORG Mon Sep 1 23:05:22 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C998616A4BF; Mon, 1 Sep 2003 23:05:22 -0700 (PDT) Received: from ns1.gnf.org (ns1.gnf.org [63.196.132.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id A157843FEA; Mon, 1 Sep 2003 23:05:21 -0700 (PDT) (envelope-from gtetlow@gnf.org) Received: from EXCHCLUSTER01.lj.gnf.org (exch02.lj.gnf.org [172.25.10.20]) by ns1.gnf.org (8.12.8p1/8.12.8) with ESMTP id h8265HtF015679; Mon, 1 Sep 2003 23:05:17 -0700 (PDT) (envelope-from gtetlow@gnf.org) Received: from roark.gnf.org ([172.25.24.15]) by EXCHCLUSTER01.lj.gnf.org with Microsoft SMTPSVC(5.0.2195.5329); Mon, 1 Sep 2003 23:05:21 -0700 Received: from roark.gnf.org (localhost [127.0.0.1]) by roark.gnf.org (8.12.9/8.12.9) with ESMTP id h8265LaH073830; Mon, 1 Sep 2003 23:05:21 -0700 (PDT) (envelope-from gtetlow@gnf.org) Received: (from gtetlow@localhost) by roark.gnf.org (8.12.9/8.12.9/Submit) id h8265Kh8073829; Mon, 1 Sep 2003 23:05:20 -0700 (PDT) (envelope-from gtetlow) Date: Mon, 1 Sep 2003 23:05:20 -0700 From: Gordon Tetlow To: deischen@freebsd.org Message-ID: <20030902060520.GX695@roark.gnf.org> References: <20030829224909.GW695@roark.gnf.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="APvmIexg9DiduZOF" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-OriginalArrivalTime: 02 Sep 2003 06:05:21.0362 (UTC) FILETIME=[311CA320:01C37118] cc: threads@freebsd.org Subject: Re: Call for thread testers X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 06:05:22 -0000 --APvmIexg9DiduZOF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 29, 2003 at 07:09:29PM -0400, Daniel Eischen wrote: > On Fri, 29 Aug 2003, Gordon Tetlow wrote: >=20 > > On Wed, Aug 27, 2003 at 09:14:28PM -0400, Daniel Eischen wrote: > > >=20 > > > OK, I've installed www/privoxy and have libmap.conf pointed at libkse. > > > It's working as far as I can tell; using the default config file. > > > I've pointed a Solaris Netscape7 at it, opened a few windows and > > > browsed a bit. How do I get it to fail? It hasn't so far. > > >=20 > > > I know I've got it working correctly, because I can see the > > > log file it is generating. > >=20 > > Hmm, for me it was easy, I just needed to go to > > www.ucomics.com/calvinandhobbes (or some other complicated (ie graphic > > intensive) page) and it did it on it's own. Not a whole lot to it. >=20 > Nope, I can't reproduce any error. I went to ucomics, and > launched a couple of other konqueror windows at the same > time going to other graphic intensive sites, and can't > reproduce any problem. Forgot to mention the rather important fact that this is a dual Athlon running an SMP kernel. -gordon --APvmIexg9DiduZOF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/VDMgRu2t9DV9ZfsRAm2ZAKCmlv4hoM3unKRT18G2uNKBb6BlbgCfZRNt 4Qk+CtA/3T0CYdp9PrcuyP0= =/T80 -----END PGP SIGNATURE----- --APvmIexg9DiduZOF-- From owner-freebsd-threads@FreeBSD.ORG Tue Sep 2 06:23:24 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6050A16A4BF for ; Tue, 2 Sep 2003 06:23:24 -0700 (PDT) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D8904400B for ; Tue, 2 Sep 2003 06:23:23 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id F23B75485D; Tue, 2 Sep 2003 08:23:22 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 8E6F46D461; Tue, 2 Sep 2003 08:23:22 -0500 (CDT) Date: Tue, 2 Sep 2003 08:23:22 -0500 From: "Jacques A. Vidrine" To: Petri Helenius Message-ID: <20030902132322.GG83746@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Petri Helenius , freebsd-threads@FreeBSD.org References: <3F4F5467.1050404@he.iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F4F5467.1050404@he.iki.fi> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-threads@FreeBSD.org Subject: Re: threads and openssl X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 13:23:24 -0000 On Fri, Aug 29, 2003 at 04:25:59PM +0300, Petri Helenius wrote: > > Is there a plan to resolve > > > bin/51205: openssl in base system is not compiled thread safe > > or has it been resolved but the pr has been left unattended? It sounds > like it would make > sense to have the library thread safe, specially in 5-CURRENT where the > threads have > a performance gain. Thanks for the reminder. I've been running with CFLAGS+= -pthread -D_REENTRANT -D_THREAD_SAFE -D_THREADSAFE in src/secure/lib/libcrypto/Makefile.inc since mid-July and I feel it is safe to commit for 5.x. I'd like to hear from others about 4.x. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se From owner-freebsd-threads@FreeBSD.ORG Tue Sep 2 06:39:37 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0017516A4C1; Tue, 2 Sep 2003 06:39:36 -0700 (PDT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id D818743FBD; Tue, 2 Sep 2003 06:39:33 -0700 (PDT) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by silver.he.iki.fi (8.12.9/8.11.4) with ESMTP id h82DdVZH099357; Tue, 2 Sep 2003 16:39:32 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <3F549D92.40008@he.iki.fi> Date: Tue, 02 Sep 2003 16:39:30 +0300 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jacques A. Vidrine" References: <3F4F5467.1050404@he.iki.fi> <20030902132322.GG83746@madman.celabo.org> In-Reply-To: <20030902132322.GG83746@madman.celabo.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-threads@FreeBSD.org Subject: Re: threads and openssl X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 13:39:37 -0000 Jacques A. Vidrine wrote: >Thanks for the reminder. I've been running with > > CFLAGS+= -pthread -D_REENTRANT -D_THREAD_SAFE -D_THREADSAFE > >in src/secure/lib/libcrypto/Makefile.inc since mid-July and I feel it >is safe to commit for 5.x. I'd like to hear from others about 4.x. > > > Personally, although I think it could prove useful in 4.x, I would be happy to have it in 5.x only, though it might be little inconsistent. Pete From owner-freebsd-threads@FreeBSD.ORG Tue Sep 2 11:21:14 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3528516A4BF for ; Tue, 2 Sep 2003 11:21:14 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B52843FD7 for ; Tue, 2 Sep 2003 11:21:13 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h82ILCZE075325; Tue, 2 Sep 2003 13:21:12 -0500 (CDT) (envelope-from dan) Date: Tue, 2 Sep 2003 13:21:12 -0500 From: Dan Nelson To: Terry Lambert Message-ID: <20030902182110.GA46649@dan.emsphone.com> References: <20030829042613.80458.qmail@web13406.mail.yahoo.com> <3F4F8D58.5F4523AE@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F4F8D58.5F4523AE@mindspring.com> X-OS: FreeBSD 5.1-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: "Pedro F. Giffuni" cc: freebsd-threads@FreeBSD.org Subject: Re: Removing -pthread from gcc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 18:21:14 -0000 In the last episode (Aug 29), Terry Lambert said: > "Pedro F. Giffuni" wrote: > > I'm not understanding what the new world order will be, but please > > try to agree something with the autoconf people: from my porting > > experience, autoconf is not interested on what PTHREAD_LIBS says; > > it just tries to link with pthread and if that fails it assumes the > > platform doesn't support threads at all. > > This is why autoconf sucks: it tries to identify the platform and > make the code conform to that, rather than identifying the platform > capabilities (note: different from "does -pthread work?") and using > that. Well, that's why badly-written autoconf tests suck. > This is why imake and xmkmf can compile every X application that > uses them, while autoconf and automake can only do it for the > platforms they have been explicitly told about. Then again, imake doesn't automatically realize that you've installed a new piece of software, or upgraded an existing one that has new capabilities or fixed bugs. > The autoconf program balkanizes things, while imake unites them. > > I wish autoconf would die. Well-written autoconf macros test for features, not platforms. There is a nice pthreads macro that tries a bunch of pthreads flags, and uses what works. It also respects the PTHREAD_LIBS and PTHREAD_CFLAGS environment variables, so it's easy to override. It's got some out-of-date tests (it tries -kthreads because it thinks FreeBSD supports it), but does work on all the systems I have available. http://www.gnu.org/software/ac-archive/htmldoc/acx_pthread.html -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-threads@FreeBSD.ORG Fri Sep 5 15:35:57 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D74D816A4BF; Fri, 5 Sep 2003 15:35:57 -0700 (PDT) Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id F19044400B; Fri, 5 Sep 2003 15:35:56 -0700 (PDT) (envelope-from rittle@latour.rsch.comm.mot.com) Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h85MZrTM029265; Fri, 5 Sep 2003 15:35:54 -0700 (MST) Received: from latour.rsch.comm.mot.com (latour.rsch.comm.mot.com [145.1.80.116])h85MZpCi013179; Fri, 5 Sep 2003 17:35:51 -0500 Received: from latour.rsch.comm.mot.com (localhost.rsch.comm.mot.com [127.0.0.1])h85MZo6e015387; Fri, 5 Sep 2003 17:35:50 -0500 (CDT) (envelope-from rittle@latour.rsch.comm.mot.com) Received: (from rittle@localhost) by latour.rsch.comm.mot.com (8.12.9/8.12.9/Submit) id h85MZoRF015386; Fri, 5 Sep 2003 17:35:50 -0500 (CDT) Date: Fri, 5 Sep 2003 17:35:50 -0500 (CDT) From: Loren James Rittle Message-Id: <200309052235.h85MZoRF015386@latour.rsch.comm.mot.com> To: eischen@vigrid.com cc: freebsd-threads@FreeBSD.org Subject: Re: Removing -pthread from gcc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2003 22:35:58 -0000 Hi Daniel, (Sorry, I read -current, -stable, -hackers to try to track changes to the system compiler. A private request came to me to make a change to the FSF tree to mirror this change.) Could you please explain this line a bit more: > If [-pthread] left in and we try to link with > libpthread,libkse,libthr, etc, we will end up with ports that link > to one of those libraries _and_ libc_r. Just try copying libkse or > libthr to libpthread _without_ changing PTHREAD_LIBS (so you still > use libc_r) and rebuilding X or KDE. You have raised a red herring. It may be true, but there has to be a better fix than breaking a 5+ year convention. If a user adds -lkse to CCFLAGS and sets the ports threads package to -lc_r, then the same problem ensues. Are you sure that this root problem is actually caused by a compiler supporting -pthread (perhaps the ports system should just stop using -pthread since was a pure alias for -lc_r before your patch)? Other systems support -pthread in gcc and have an -lpthread yet do not display the issue you describe. Why is FreeBSD special in having that problem? Perhaps -pthread should be mapped to -lpthread instead of -lc_r (upon a flag day, etc.), if that could help the situation. Please do not use a current shortcoming in ports(5) to kill a portability feature of gcc. A claim has been floated that -pthread is not standard. I tell you that is not the intention of the FSF gcc team, even if it is poorly documented. Since gcc 3.0 (some have been added post 3.0 release over time): -pthread is supported on Linux (I believe actually copied from FreeBSD even though they never had the switch -lc to issue). -pthread is supported on HPUX (both PA and ia64). -pthreads (note misspelt but same feature) is supported on Solaris. -pthread supported on OpenBSD and NetBSD. -pthread is supported on OSF/alpha. -pthread is supported on SysV/i386 and /PPC. -pthread is supported on AIX. Typically, -mthread[s] (don't ask) is supported if the port supports threads but not POSIX threads. Even ports that merely add a library instead of replace a library support the switch. "Everyone" in the BSD world claims to hate autoconf, libtool; yet removal of this -pthread feature leads away from emerging standardization in gcc not towards it. Such balkanization will actually require more special cases for FreeBSD in such tools not less. I will fix the FSF documentation for gcc, if you were led astray by the explicit references to AIX but none other. If you are unmoved by my line of argument, then I hereby promise to commit the change such that it hits the FSF gcc 3.4 release. Upon review, I can't honor any request to make it hit the FSF gcc 3.3.2 release since we don't revoke features in point releases in that tree. Thank you for considering these words. BTW, wouldn't it be cooler if (example only): -pthread (whatever the system default) -pthread=1 (1 process, aka -lc_r) -pthread=1:1 (1 process per thread, aka -lthr) -pthread=M:N (M threads in N processes, aka -lkse) -pthread=late/weak (perhaps not good ELF form, link against a stub to which all POSIX thread libraries on FreeBSD must conform, do not record the dependency ala FreeBSD4 default for -lc; or that does it in a weak manner en mass such that binding is deferred to the final selection made at a final link time) I suspect that late/weak could be quite useful for building ports and allowing the final application link to select the thread implementation via the final specification. BTW, I'm the libstdc++-v3 maintainer that did a lot of the threading improvements in the FSF tree (basically made threaded-C++ work as well or better than Linux IMHO ;-) so I hope I'm a stakeholder here. When built in the FSF tree (and I suspect the FreeBSD system tree), libstdc++-v3 is setup to do late binding as I'm proposing as a generic feature above. On FreeBSD 4-STABLE, 5-CURRENT similar: ; ldd /usr/local/beta-gcc/lib/libstdc++.so.6: libm.so.2 => /usr/lib/libm.so.2 (0x28177000) libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1 (0x28193000) ; nm /usr/local/beta-gcc/lib/libstdc++.so.6 |grep pthread 00058bc4 T _ZNSt12__basic_fileIcEC1EPP13pthread_mutex 00058bb0 T _ZNSt12__basic_fileIcEC2EPP13pthread_mutex w pthread_create w pthread_getspecific w pthread_key_create w pthread_mutex_lock w pthread_mutex_unlock w pthread_once w pthread_setspecific It is possible that there are unknown snags with this approach. E.g. The weakness property was applied at the source level of the library. It may not be possible to make a library that claims to export various symbols yet are really weak placeholders. I am not an ELF expert; I only know enough to be dangerous... ;-) Regards, Loren From owner-freebsd-threads@FreeBSD.ORG Fri Sep 5 16:47:04 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14B0316A4BF; Fri, 5 Sep 2003 16:47:04 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2910A43FF9; Fri, 5 Sep 2003 16:47:02 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h85Nl1tp005986; Fri, 5 Sep 2003 19:47:01 -0400 (EDT) Date: Fri, 5 Sep 2003 19:47:01 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Loren James Rittle In-Reply-To: <200309052235.h85MZoRF015386@latour.rsch.comm.mot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: jb@FreeBSD.org cc: freebsd-threads@FreeBSD.org Subject: Re: Removing -pthread from gcc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@FreeBSD.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2003 23:47:04 -0000 John Birrell CC'd to help explain the history of -pthread. On Fri, 5 Sep 2003, Loren James Rittle wrote: > Hi Daniel, > > (Sorry, I read -current, -stable, -hackers to try to track changes to > the system compiler. A private request came to me to make a change to > the FSF tree to mirror this change.) > > Could you please explain this line a bit more: > > > If [-pthread] left in and we try to link with > > libpthread,libkse,libthr, etc, we will end up with ports that link > > to one of those libraries _and_ libc_r. Just try copying libkse or > > libthr to libpthread _without_ changing PTHREAD_LIBS (so you still > > use libc_r) and rebuilding X or KDE. > > You have raised a red herring. It may be true, but there has to be a > better fix than breaking a 5+ year convention. If a user adds -lkse > to CCFLAGS and sets the ports threads package to -lc_r, then the same > problem ensues. Are you sure that this root problem is actually > caused by a compiler supporting -pthread (perhaps the ports system > should just stop using -pthread since was a pure alias for -lc_r > before your patch)? Other systems support -pthread in gcc and have an > -lpthread yet do not display the issue you describe. Why is FreeBSD > special in having that problem? Perhaps -pthread should be mapped to > -lpthread instead of -lc_r (upon a flag day, etc.), if that could help > the situation. The problem is that -pthread maps to one threads library, and we have multiple threads libraries from which to choose. We have libc_r, libkse (M:N mode), libkse (1:1 mode), and libthr. -pthread arose (in FreeBSD anyways) because you couldn't link to both libc and libc_r in FreeBSD-[34]. In FreeBSD-5+, we don't need -pthread. In other words, -pthread was replaced by -lthr, -lkse11, -lkseMN, or -lc_r. The one dimensional -pthread doesn't serve us any longer. I would have less of an objection if -pthread were kept in but made a NOOP. > Please do not use a current shortcoming in ports(5) to kill a > portability feature of gcc. A claim has been floated that -pthread is > not standard. I tell you that is not the intention of the FSF gcc > team, even if it is poorly documented. Since gcc 3.0 (some have been > added post 3.0 release over time): > > -pthread is supported on Linux (I believe actually copied from FreeBSD > even though they never had the switch -lc to issue). > "Everyone" in the BSD world claims to hate autoconf, libtool; yet > removal of this -pthread feature leads away from emerging > standardization in gcc not towards it. Such balkanization will > actually require more special cases for FreeBSD in such tools not less. Most of the autoconfs I have seen check for -lpthread, and -lthread, even -lc_r. Once FreeBSD renames libkse(M:N) to libpthread, autoconf should be unbroken, probably libtool also. We could have thrown the switch from libkse to libpthread at the same time as -pthread was removed from our repo, but (mostly) I didn't do it so that "shortcoming in ports" could be easily found and fixed. > I will fix the FSF documentation for gcc, if you were led astray by > the explicit references to AIX but none other. > > If you are unmoved by my line of argument, then I hereby promise to > commit the change such that it hits the FSF gcc 3.4 release. Upon > review, I can't honor any request to make it hit the FSF gcc 3.3.2 > release since we don't revoke features in point releases in that tree. > > Thank you for considering these words. BTW, wouldn't it be cooler > if (example only): > > -pthread (whatever the system default) > -pthread=1 (1 process, aka -lc_r) > -pthread=1:1 (1 process per thread, aka -lthr) > -pthread=M:N (M threads in N processes, aka -lkse) > -pthread=late/weak (perhaps not good ELF form, link against a stub to > which all POSIX thread libraries on FreeBSD must conform, do not > record the dependency ala FreeBSD4 default for -lc; or that does it in > a weak manner en mass such that binding is deferred to the final > selection made at a final link time) That's a lot better :-) The only problem is that we have 2 different libraries that offer 1:1... I would not object to this approach, but I would like to temporarily make -pthread (without args) either a NOOP or an error in our tree to help correct "shortcoming in ports". > I suspect that late/weak could be quite useful for building ports and > allowing the final application link to select the thread > implementation via the final specification. BTW, I'm the libstdc++-v3 > maintainer that did a lot of the threading improvements in the FSF > tree (basically made threaded-C++ work as well or better than Linux > IMHO ;-) so I hope I'm a stakeholder here. When built in the FSF tree > (and I suspect the FreeBSD system tree), libstdc++-v3 is setup to do > late binding as I'm proposing as a generic feature above. > > On FreeBSD 4-STABLE, 5-CURRENT similar: > > ; ldd /usr/local/beta-gcc/lib/libstdc++.so.6: > libm.so.2 => /usr/lib/libm.so.2 (0x28177000) > libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1 (0x28193000) > > ; nm /usr/local/beta-gcc/lib/libstdc++.so.6 |grep pthread > 00058bc4 T _ZNSt12__basic_fileIcEC1EPP13pthread_mutex > 00058bb0 T _ZNSt12__basic_fileIcEC2EPP13pthread_mutex > w pthread_create > w pthread_getspecific > w pthread_key_create > w pthread_mutex_lock > w pthread_mutex_unlock > w pthread_once > w pthread_setspecific > > It is possible that there are unknown snags with this approach. > E.g. The weakness property was applied at the source level of the > library. It may not be possible to make a library that claims to > export various symbols yet are really weak placeholders. I am not an > ELF expert; I only know enough to be dangerous... ;-) I suppose kan might have something to say about this. -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Fri Sep 5 17:07:11 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CD4316A4BF; Fri, 5 Sep 2003 17:07:11 -0700 (PDT) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B5EC43FE1; Fri, 5 Sep 2003 17:07:05 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: from freebsd1.cimlogic.com.au (localhost [127.0.0.1]) by cimlogic.com.au (8.12.9/8.12.9) with ESMTP id h86092bZ031851; Sat, 6 Sep 2003 10:09:02 +1000 (EST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.12.9/8.12.9/Submit) id h86092fm031850; Sat, 6 Sep 2003 10:09:02 +1000 (EST) Date: Sat, 6 Sep 2003 10:09:02 +1000 From: John Birrell To: deischen@FreeBSD.org Message-ID: <20030906000902.GA25237@freebsd1.cimlogic.com.au> References: <200309052235.h85MZoRF015386@latour.rsch.comm.mot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: jb@FreeBSD.org cc: Loren James Rittle cc: freebsd-threads@FreeBSD.org Subject: Re: Removing -pthread from gcc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 00:07:11 -0000 On Fri, Sep 05, 2003 at 07:47:01PM -0400, Daniel Eischen wrote: > -pthread arose (in FreeBSD anyways) because you couldn't link > to both libc and libc_r in FreeBSD-[34]. In FreeBSD-5+, > we don't need -pthread. In other words, -pthread was replaced > by -lthr, -lkse11, -lkseMN, or -lc_r. The one dimensional > -pthread doesn't serve us any longer. > > I would have less of an objection if -pthread were kept in > but made a NOOP. > > > Please do not use a current shortcoming in ports(5) to kill a > > portability feature of gcc. A claim has been floated that -pthread is > > not standard. I tell you that is not the intention of the FSF gcc > > team, even if it is poorly documented. Since gcc 3.0 (some have been > > added post 3.0 release over time): > > > > -pthread is supported on Linux (I believe actually copied from FreeBSD > > even though they never had the switch -lc to issue). If -pthread is intended as a standard FSF gcc option, then it should be mapped to a NOOP for FreeBSD IMO. Back at the time when -pthread was added to FreeBSD's gcc (prior to being adopted by the FSF) the FreeBSD libc maintainers didn't want pthread stubs in libc, so an alternative library had to be built. The name came from OSF1. Since gcc 'knew' about libc, the only viable alternative was to also teach gcc about libc_r, hence the -pthread argument. I've just been through the exercise removing -pthread from my local application sources using the -current gcc which spits if -pthread is still used. From what I can see, this needn't be an error (or even a warning), because if the application uses one or more of the pthread functions (other than the ones which are stubbed), all you get is a link error. I think this still makes it obvious to ports people what is going on. So a NOOP is best. Change gcc in the FSF sources when appropriate, but let -current have the change now. -- John Birrell From owner-freebsd-threads@FreeBSD.ORG Fri Sep 5 17:18:24 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB91B16A4BF; Fri, 5 Sep 2003 17:18:24 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2385043F75; Fri, 5 Sep 2003 17:18:24 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h860I8tp010516; Fri, 5 Sep 2003 20:18:08 -0400 (EDT) Date: Fri, 5 Sep 2003 20:18:08 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: John Birrell In-Reply-To: <20030906000902.GA25237@freebsd1.cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: jb@FreeBSD.org cc: Loren James Rittle cc: freebsd-threads@FreeBSD.org Subject: Re: Removing -pthread from gcc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@FreeBSD.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 00:18:25 -0000 On Sat, 6 Sep 2003, John Birrell wrote: > On Fri, Sep 05, 2003 at 07:47:01PM -0400, Daniel Eischen wrote: > > -pthread arose (in FreeBSD anyways) because you couldn't link > > to both libc and libc_r in FreeBSD-[34]. In FreeBSD-5+, > > we don't need -pthread. In other words, -pthread was replaced > > by -lthr, -lkse11, -lkseMN, or -lc_r. The one dimensional > > -pthread doesn't serve us any longer. > > > > I would have less of an objection if -pthread were kept in > > but made a NOOP. > > > > > Please do not use a current shortcoming in ports(5) to kill a > > > portability feature of gcc. A claim has been floated that -pthread is > > > not standard. I tell you that is not the intention of the FSF gcc > > > team, even if it is poorly documented. Since gcc 3.0 (some have been > > > added post 3.0 release over time): > > > > > > -pthread is supported on Linux (I believe actually copied from FreeBSD > > > even though they never had the switch -lc to issue). > > If -pthread is intended as a standard FSF gcc option, then it should be mapped > to a NOOP for FreeBSD IMO. > > Back at the time when -pthread was added to FreeBSD's gcc (prior to being > adopted by the FSF) the FreeBSD libc maintainers didn't want pthread stubs > in libc, so an alternative library had to be built. The name came from OSF1. > > Since gcc 'knew' about libc, the only viable alternative was to also teach > gcc about libc_r, hence the -pthread argument. > > I've just been through the exercise removing -pthread from my local application > sources using the -current gcc which spits if -pthread is still used. From what > I can see, this needn't be an error (or even a warning), because if the > application uses one or more of the pthread functions (other than the ones > which are stubbed), all you get is a link error. I think this still makes it > obvious to ports people what is going on. If you link an application, then it will. But if you are linking a library (OpenGL, libgthread, etc), I don't think you will get the error. > So a NOOP is best. Change gcc in the FSF sources when appropriate, but let > -current have the change now. -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Fri Sep 5 17:26:40 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8135616A4BF; Fri, 5 Sep 2003 17:26:40 -0700 (PDT) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D97743FEA; Fri, 5 Sep 2003 17:26:37 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: from freebsd1.cimlogic.com.au (localhost [127.0.0.1]) by cimlogic.com.au (8.12.9/8.12.9) with ESMTP id h860SabZ031938; Sat, 6 Sep 2003 10:28:36 +1000 (EST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.12.9/8.12.9/Submit) id h860Sapr031937; Sat, 6 Sep 2003 10:28:36 +1000 (EST) Date: Sat, 6 Sep 2003 10:28:36 +1000 From: John Birrell To: deischen@FreeBSD.org Message-ID: <20030906002836.GB25237@freebsd1.cimlogic.com.au> References: <20030906000902.GA25237@freebsd1.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: Loren James Rittle cc: freebsd-threads@FreeBSD.org Subject: Re: Removing -pthread from gcc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 00:26:40 -0000 On Fri, Sep 05, 2003 at 08:18:08PM -0400, Daniel Eischen wrote: > If you link an application, then it will. But if you are linking > a library (OpenGL, libgthread, etc), I don't think you will get > the error. Why do you need an error when you build the library? Presumably ports people actually run the libraries that they build with an application to test them. If the thread functions don't resolve, you'll get a runtime error stating which library contained an unresolved reference. I think these things have a way of working themselves out without having to be too clever. 8-) -- John Birrell From owner-freebsd-threads@FreeBSD.ORG Fri Sep 5 17:31:48 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAC8416A4BF for ; Fri, 5 Sep 2003 17:31:48 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4C3143FCB for ; Fri, 5 Sep 2003 17:31:47 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h860Vdtp012458; Fri, 5 Sep 2003 20:31:40 -0400 (EDT) Date: Fri, 5 Sep 2003 20:31:39 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: John Birrell In-Reply-To: <20030906002836.GB25237@freebsd1.cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Loren James Rittle cc: freebsd-threads@FreeBSD.org Subject: Re: Removing -pthread from gcc X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@FreeBSD.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 00:31:48 -0000 On Sat, 6 Sep 2003, John Birrell wrote: > On Fri, Sep 05, 2003 at 08:18:08PM -0400, Daniel Eischen wrote: > > If you link an application, then it will. But if you are linking > > a library (OpenGL, libgthread, etc), I don't think you will get > > the error. > > Why do you need an error when you build the library? Presumably ports > people actually run the libraries that they build with an application > to test them. If the thread functions don't resolve, you'll get a > runtime error stating which library contained an unresolved reference. > I think these things have a way of working themselves out without having > to be too clever. 8-) Yes, it's just easier if the port to which the library belongs breaks, not the port to which the application belongs. Also, some ports build with both -pthread and -lc_r, so NOOPing -pthread wouldn't break those ports. But that's probably another issue altogether :( -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Sat Sep 6 04:40:53 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E313F16A4BF for ; Sat, 6 Sep 2003 04:40:53 -0700 (PDT) Received: from merke.itea.ntnu.no (merke.itea.ntnu.no [129.241.7.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D3AF43FE3 for ; Sat, 6 Sep 2003 04:40:52 -0700 (PDT) (envelope-from morten@rodal.no) Received: from localhost (localhost [127.0.0.1]) by merke.itea.ntnu.no (Postfix) with ESMTP id B434EC6F54 for ; Sat, 6 Sep 2003 13:40:50 +0200 (CEST) Received: from atlantis.rodal.no (m137h.studby.ntnu.no [129.241.135.137]) by merke.itea.ntnu.no (Postfix) with ESMTP id 78CE6C6F4D for ; Sat, 6 Sep 2003 13:40:50 +0200 (CEST) Received: (from morten@localhost) by atlantis.rodal.no (8.12.9/8.12.9/Submit) id h86BeoOg081066 for threads@freebsd.org; Sat, 6 Sep 2003 13:40:50 +0200 (CEST) (envelope-from morten) Date: Sat, 6 Sep 2003 13:40:50 +0200 From: Morten Rodal To: threads@freebsd.org Message-ID: <20030906114048.GA598@atlantis.rodal.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Subject: libthr/libkse and Mozilla Firebird X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 11:40:54 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Howdy! Is Mozilla Firebird (www/mozilla-firebird ; firebird-gtk2-0.6.1_1) supposed to work with either libthr or libkse? With libthr I get it to work for a little while before it deadlocks and I have to kill it (with SIGKILL). While with libkse it works, for a little while. After starting up I can perhaps render half a page, sometimes a two or three pages, before firebird just exits. Nothing is printed on the console and no core dump is found, it is as if the program just called exit(2). I wish I could provide more detailed debugging, but I am having trouble getting firebird to run from within gdb.. This happens on both SMP and singel processor machines. For the record, it _USED_ to work with libkse. But after the ATAng update I was forced to upgrade my kernel a few times and now I have lost the date when it used to work. Am I the only one not getting firebird to work? --=20 Morten Rodal --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/WcfAbWe1Cy11WVsRAkmtAKDN1wszRJHjFltiU/FPVwFl8AfGgQCg4p7l WOh/cMwRxr5/tleo7lw8cwU= =NESI -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-threads@FreeBSD.ORG Sat Sep 6 04:50:09 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08B8F16A4BF; Sat, 6 Sep 2003 04:50:09 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AC194400E; Sat, 6 Sep 2003 04:50:08 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h86Bo7tp013439; Sat, 6 Sep 2003 07:50:07 -0400 (EDT) Date: Sat, 6 Sep 2003 07:50:07 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Morten Rodal In-Reply-To: <20030906114048.GA598@atlantis.rodal.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: davidxu@freebsd.org Subject: Re: libthr/libkse and Mozilla Firebird X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 11:50:09 -0000 On Sat, 6 Sep 2003, Morten Rodal wrote: > Howdy! > > Is Mozilla Firebird (www/mozilla-firebird ; firebird-gtk2-0.6.1_1) > supposed to work with either libthr or libkse? > > With libthr I get it to work for a little while before it deadlocks > and I have to kill it (with SIGKILL). > > While with libkse it works, for a little while. After starting up I > can perhaps render half a page, sometimes a two or three pages, before > firebird just exits. Nothing is printed on the console and no core > dump is found, it is as if the program just called exit(2). I wish I > could provide more detailed debugging, but I am having trouble getting > firebird to run from within gdb.. > > This happens on both SMP and singel processor machines. > > For the record, it _USED_ to work with libkse. But after the ATAng > update I was forced to upgrade my kernel a few times and now I have > lost the date when it used to work. Am I the only one not getting > firebird to work? Have you tried updating libpthread very recently (yesterday?). There was a commit a few days ago that broke libpthread; kde wouldn't even work. I'm not sure if it has been fixed yet, but there was a commit yesterday that may have fixed it. David or kan should know... -- Dan Eischen From owner-freebsd-threads@FreeBSD.ORG Sat Sep 6 05:41:12 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F35A16A4BF; Sat, 6 Sep 2003 05:41:12 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0410F44003; Sat, 6 Sep 2003 05:41:12 -0700 (PDT) (envelope-from davidxu@FreeBSD.org) Received: from localhost (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h86Cf8Up028696; Sat, 6 Sep 2003 05:41:09 -0700 (PDT) (envelope-from davidxu@FreeBSD.org) From: David Xu To: deischen@FreeBSD.org, Daniel Eischen , Morten Rodal Date: Sat, 6 Sep 2003 20:44:03 +0800 User-Agent: KMail/1.5.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200309062043.38217.davidxu@FreeBSD.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit cc: threads@FreeBSD.org Subject: Re: libthr/libkse and Mozilla Firebird X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: davidxu@FreeBSD.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 12:41:12 -0000 On Saturday 06 September 2003 19:50, Daniel Eischen wrote: > Have you tried updating libpthread very recently (yesterday?). > There was a commit a few days ago that broke libpthread; kde > wouldn't even work. I'm not sure if it has been fixed yet, > but there was a commit yesterday that may have fixed it. > David or kan should know... Yes, the problem seems be fixed, it works fine now. David Xu From owner-freebsd-threads@FreeBSD.ORG Sat Sep 6 05:52:07 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D10416A4BF; Sat, 6 Sep 2003 05:52:07 -0700 (PDT) Received: from merke.itea.ntnu.no (merke.itea.ntnu.no [129.241.7.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 231DF43FDD; Sat, 6 Sep 2003 05:52:06 -0700 (PDT) (envelope-from morten@rodal.no) Received: from localhost (localhost [127.0.0.1]) by merke.itea.ntnu.no (Postfix) with ESMTP id 9EE1CC6F55; Sat, 6 Sep 2003 14:52:04 +0200 (CEST) Received: from atlantis.rodal.no (m137h.studby.ntnu.no [129.241.135.137]) by merke.itea.ntnu.no (Postfix) with ESMTP id 5E8A2C6F54; Sat, 6 Sep 2003 14:52:04 +0200 (CEST) Received: (from morten@localhost) by atlantis.rodal.no (8.12.9/8.12.9/Submit) id h86Cq3If082750; Sat, 6 Sep 2003 14:52:03 +0200 (CEST) (envelope-from morten) Date: Sat, 6 Sep 2003 14:52:03 +0200 From: Morten Rodal To: David Xu Message-ID: <20030906125203.GB598@atlantis.rodal.no> References: <200309062043.38217.davidxu@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cvVnyQ+4j833TQvp" Content-Disposition: inline In-Reply-To: <200309062043.38217.davidxu@FreeBSD.org> X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. cc: threads@FreeBSD.org Subject: Re: libthr/libkse and Mozilla Firebird X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 12:52:07 -0000 --cvVnyQ+4j833TQvp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 06, 2003 at 08:44:03PM +0800, David Xu wrote: > On Saturday 06 September 2003 19:50, Daniel Eischen wrote: > > Have you tried updating libpthread very recently (yesterday?). > > There was a commit a few days ago that broke libpthread; kde > > wouldn't even work. I'm not sure if it has been fixed yet, > > but there was a commit yesterday that may have fixed it. > > David or kan should know... >=20 > Yes, the problem seems be fixed, it works fine now. >=20 I can confirm that firebird seems to work (just rebuilt my libpthread and installed it). But only on my laptop. On my desktop, which is an SMP machine, it still exits without a trace. Performance wise I would really like to see libkse work with mozilla on my desktop since it is _MUCH_ better on the laptop. --=20 Morten Rodal --cvVnyQ+4j833TQvp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/WdhzbWe1Cy11WVsRAkclAKDWj5tz7WCFwZwfimAoeFsrH6esgACfUjdq YUTI1SFFXtUzVGVjFlU0i0Y= =PGJ2 -----END PGP SIGNATURE----- --cvVnyQ+4j833TQvp-- From owner-freebsd-threads@FreeBSD.ORG Sat Sep 6 14:58:52 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96E0716A4BF for ; Sat, 6 Sep 2003 14:58:52 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id B953543FE3 for ; Sat, 6 Sep 2003 14:58:49 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfirp.dialup.mindspring.com ([165.247.203.121] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19vl4u-0000Xy-00; Sat, 06 Sep 2003 14:58:45 -0700 Message-ID: <3F5A5852.CF901356@mindspring.com> Date: Sat, 06 Sep 2003 14:57:38 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Morten Rodal References: <20030906114048.GA598@atlantis.rodal.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4483b7d580a02985a2da4aeb3332bb4db350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: threads@freebsd.org Subject: Re: libthr/libkse and Mozilla Firebird X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 21:58:52 -0000 Morten Rodal wrote: > Is Mozilla Firebird (www/mozilla-firebird ; firebird-gtk2-0.6.1_1) > supposed to work with either libthr or libkse? > > While with libkse it works, for a little while. After starting up I > can perhaps render half a page, sometimes a two or three pages, before > firebird just exits. Nothing is printed on the console and no core > dump is found, it is as if the program just called exit(2). I wish I > could provide more detailed debugging, but I am having trouble getting > firebird to run from within gdb.. If you don't move the mouse until the page is finished loading, does it work? If so, you need Daniel Eishen's patch to the scheduler to make it operate in FIFO order instead of priority order. Historically, the image rendering code in Netscape hasn't been thread-safe, and it may be that Mozilla has inherited this infirmity. -- Terry From owner-freebsd-threads@FreeBSD.ORG Sat Sep 6 16:10:13 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5699C16A4BF for ; Sat, 6 Sep 2003 16:10:13 -0700 (PDT) Received: from merke.itea.ntnu.no (merke.itea.ntnu.no [129.241.7.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4581343FE1 for ; Sat, 6 Sep 2003 16:10:11 -0700 (PDT) (envelope-from morten@rodal.no) Received: from localhost (localhost [127.0.0.1]) by merke.itea.ntnu.no (Postfix) with ESMTP id DD27EC6F50; Sun, 7 Sep 2003 01:10:09 +0200 (CEST) Received: from slurp.rodal.no (m200h.studby.ntnu.no [129.241.135.200]) by merke.itea.ntnu.no (Postfix) with ESMTP id 9680FC6F4D; Sun, 7 Sep 2003 01:10:09 +0200 (CEST) Received: (from morten@localhost) by slurp.rodal.no (8.12.9/8.12.9/Submit) id h86NA8oS055385; Sun, 7 Sep 2003 01:10:08 +0200 (CEST) (envelope-from morten) Date: Sun, 7 Sep 2003 01:10:08 +0200 From: Morten Rodal To: Terry Lambert Message-ID: <20030906231008.GA55221@slurp.rodal.no> References: <20030906114048.GA598@atlantis.rodal.no> <3F5A5852.CF901356@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline In-Reply-To: <3F5A5852.CF901356@mindspring.com> X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. cc: threads@freebsd.org Subject: Re: libthr/libkse and Mozilla Firebird X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 23:10:13 -0000 --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 06, 2003 at 02:57:38PM -0700, Terry Lambert wrote: > Morten Rodal wrote: > > Is Mozilla Firebird (www/mozilla-firebird ; firebird-gtk2-0.6.1_1) > > supposed to work with either libthr or libkse? > >=20 > > While with libkse it works, for a little while. After starting up I > > can perhaps render half a page, sometimes a two or three pages, before > > firebird just exits. Nothing is printed on the console and no core > > dump is found, it is as if the program just called exit(2). I wish I > > could provide more detailed debugging, but I am having trouble getting > > firebird to run from within gdb.. >=20 > If you don't move the mouse until the page is finished loading, > does it work? >=20 I tried browsing without the mouse (kinda hard actually), but I was still able to get it to "crash." > If so, you need Daniel Eishen's patch to the scheduler to make it > operate in FIFO order instead of priority order. Historically, the > image rendering code in Netscape hasn't been thread-safe, and it > may be that Mozilla has inherited this infirmity. > Is there a performance impact on this patch? As for the images, I think you might be on to something there. As it seems to be more likely to crash on pages with many images. --=20 Morten Rodal --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/WmlPbWe1Cy11WVsRAmN0AKDI0kVjdXzyzNRF+kgLMf9nyzo1JwCffkzp 99QBXNJZb67p9lDiJ4Wy2BY= =TA6o -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e-- From owner-freebsd-threads@FreeBSD.ORG Sat Sep 6 22:31:48 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B193716A4C0 for ; Sat, 6 Sep 2003 22:31:48 -0700 (PDT) Received: from smtp015.mail.yahoo.com (smtp015.mail.yahoo.com [216.136.173.59]) by mx1.FreeBSD.org (Postfix) with SMTP id 48F1543F93 for ; Sat, 6 Sep 2003 22:31:47 -0700 (PDT) (envelope-from kaeru@pd.jaring.my) Received: from unknown (HELO ?219.95.208.247?) (khairil?yusof@219.95.208.247 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 7 Sep 2003 05:31:46 -0000 From: Khairil Yusof To: Morten Rodal In-Reply-To: <20030906125203.GB598@atlantis.rodal.no> References: <200309062043.38217.davidxu@FreeBSD.org> <20030906125203.GB598@atlantis.rodal.no> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-UonQ3Y5rRxWnBV1J3b2h" Message-Id: <1062912702.64411.7.camel@wolverine.home.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Sun, 07 Sep 2003 13:31:43 +0800 cc: threads@FreeBSD.org Subject: Re: libthr/libkse and Mozilla Firebird X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2003 05:31:48 -0000 --=-UonQ3Y5rRxWnBV1J3b2h Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2003-09-06 at 20:52, Morten Rodal wrote: > But only on my laptop. On my desktop, which is an > SMP machine, it still exits without a trace. Performance wise I would > really like to see libkse work with mozilla on my desktop since it is > _MUCH_ better on the laptop. I can confirm that with libpthreads rebuilt 17hrs ago, that mozilla-firebird + libkse + smp works, so is every other app that is using libc_r on my system mapped to libkse. Until the latest fixes, top would show one libkse related process as stuck in *Giant. When this happens then not just firebird but everything else libkse related would start acting funny (gkrellm, evolution would hang, crash etc.) Everything works well again now, and joe marcus clarke just commited fixes to hardcoded -pthread in mozilla related ports, to allow it to build on current. -- "Optimized, readable, on time; Pick any two."=20 FreeBSD 5.1-CURRENT i386=20 1:23PM up 16:15, 2 users, load averages: 1.04, 0.59, 0.43 --=-UonQ3Y5rRxWnBV1J3b2h Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/WsK+DAqnLW/+/X8RAjL5AKCRrdT0U7GteeRLe+dyriMoosIlvACg6aWs kwbQKDrkpOazruQjCbQ+Nzc= =HWAr -----END PGP SIGNATURE----- --=-UonQ3Y5rRxWnBV1J3b2h--