From owner-freebsd-threads@FreeBSD.ORG Mon Jun 13 11:02:19 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 D561F16A420 for ; Mon, 13 Jun 2005 11:02:19 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E9FD43D5C for ; Mon, 13 Jun 2005 11:02:19 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5DB2IuP046323 for ; Mon, 13 Jun 2005 11:02:18 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j5DB2IxO046318 for freebsd-threads@freebsd.org; Mon, 13 Jun 2005 11:02:18 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 13 Jun 2005 11:02:18 GMT Message-Id: <200506131102.j5DB2IxO046318@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 Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 11:02:20 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/01/26] threads/76690threads fork hang in child for (-lc_r & -lthr) o [2005/05/11] threads/80887threads ULE with SMP broke libpthread/libthr on 5 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/07/18] kern/20016 threads pthreads: Cannot set scheduling timer/Can o [2000/08/08] threads/20490threads Termios timeout parameters, VMIN, VTIME, o [2000/08/26] kern/20861 threads libc_r does not honor socket timeouts o [2001/01/20] threads/24472threads libc_r does not honor SO_SNDTIMEO/SO_RCVT o [2001/01/25] threads/24632threads libc_r delicate deviation from libc in ha o [2001/01/25] kern/24641 threads pthread_rwlock_rdlock can deadlock o [2001/11/26] bin/32295 threads pthread dont dequeue signals o [2002/02/01] threads/34536threads accept() blocks other threads o [2002/05/25] kern/38549 threads the procces compiled whith pthread stoppe o [2002/06/27] threads/39922threads [PATCH?] Threaded applications executed w o [2002/08/04] kern/41331 threads Pthread library open sets O_NONBLOCK flag o [2003/03/02] threads/48856threads Setting SIGCHLD to SIG_IGN still leaves z o [2003/03/10] threads/49087threads Signals lost in programs linked with libc o [2003/05/08] threads/51949threads thread in accept cannot be cancelled s [2004/03/15] kern/64313 threads FreeBSD (OpenBSD) pthread implicit set/un o [2004/08/26] threads/70975threads unexpected and unreliable behaviour when o [2004/09/14] threads/71725threads Mysql Crashes frequently giving Sock Erro o [2004/10/05] threads/72353threads Assertion fails in /usr/src/lib/libpthrea o [2004/10/07] threads/72429threads threads blocked in stdio (fgets, etc) are o [2004/10/21] threads/72953threads fork() unblocks blocked signals w/o PTHRE o [2004/12/19] threads/75273threads FBSD 5.3 libpthread (KSE) bug o [2004/12/21] threads/75374threads pthread_kill() ignores SA_SIGINFO flag o [2005/01/26] threads/76694threads fork cause hang in dup()/close() function o [2005/03/10] threads/78660threads Java hangs unkillably in STOP state after o [2005/04/08] threads/79683threads svctcp_create() fails if multiple threads o [2005/04/28] threads/80435threads panic on high loads o [2005/05/19] threads/81258threads Thread specific data is sometimes assigne 27 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/05/26] kern/18824 threads gethostbyname is not thread safe o [2000/06/13] kern/19247 threads uthread_sigaction.c does not do anything o [2000/10/21] kern/22190 threads A threaded read(2) from a socketpair(2) f o [2001/09/09] threads/30464threads pthread mutex attributes -- pshared o [2002/05/02] threads/37676threads libc_r: msgsnd(), msgrcv(), pread(), pwri s [2002/07/16] threads/40671threads pthread_cancel doesn't remove thread from o [2004/07/13] threads/69020threads pthreads library leaks _gc_mutex o [2004/09/21] threads/71966threads Mlnet Core Dumped : Fatal error '_pq_inse o [2004/11/21] threads/74180threads KSE problem. Applications those riched ma o [2005/01/20] threads/76513threads libpthread is not working o [2005/04/13] threads/79887threads [patch] freopen() isn't thread-safe o [2005/05/13] threads/80992threads abort() sometimes not caught by gdb depen o [2005/05/26] threads/81534threads [PATCH] libc_r close() will fail on any f 13 problems total. From owner-freebsd-threads@FreeBSD.ORG Mon Jun 13 15:09:53 2005 Return-Path: X-Original-To: freebsd-threads@FreeBSD.org 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 8B7BD16A44C; Mon, 13 Jun 2005 15:09:53 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3760A43D48; Mon, 13 Jun 2005 15:09:53 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.50 (FreeBSD)) id 1DhqZU-000KKT-BF; Mon, 13 Jun 2005 16:09:52 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.50 (FreeBSD)) id 1DhqZU-0000Jv-A8; Mon, 13 Jun 2005 16:09:52 +0100 To: bug-followup@FreeBSD.org, freebsd-threads@FreeBSD.org In-Reply-To: <200505131740.j4DHe2gt043880@freefall.freebsd.org> Message-Id: From: Pete French Date: Mon, 13 Jun 2005 16:09:52 +0100 Cc: Subject: Re: threads/80992: abort() sometimes not caught by gdb depending on thread library X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 15:09:53 -0000 A bit more info - this problem seems to be related to the scope of the threads as if I run the test program with LIBPTHREAD_SYSTEM_SCOPE defined then the debugger catches the abort correctly and lets me trace the offending method call. From owner-freebsd-threads@FreeBSD.ORG Mon Jun 13 15:10:07 2005 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9075516A41C for ; Mon, 13 Jun 2005 15:10:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5642D43D48 for ; Mon, 13 Jun 2005 15:10:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5DFA7FG082470 for ; Mon, 13 Jun 2005 15:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j5DFA7dA082469; Mon, 13 Jun 2005 15:10:07 GMT (envelope-from gnats) Date: Mon, 13 Jun 2005 15:10:07 GMT Message-Id: <200506131510.j5DFA7dA082469@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Pete French Cc: Subject: Re: threads/80992: abort() sometimes not caught by gdb depending on thread library X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pete French List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 15:10:07 -0000 The following reply was made to PR threads/80992; it has been noted by GNATS. From: Pete French To: bug-followup@FreeBSD.org, freebsd-threads@FreeBSD.org Cc: Subject: Re: threads/80992: abort() sometimes not caught by gdb depending on thread library Date: Mon, 13 Jun 2005 16:09:52 +0100 A bit more info - this problem seems to be related to the scope of the threads as if I run the test program with LIBPTHREAD_SYSTEM_SCOPE defined then the debugger catches the abort correctly and lets me trace the offending method call. From owner-freebsd-threads@FreeBSD.ORG Tue Jun 14 02:48:05 2005 Return-Path: X-Original-To: freebsd-threads@FreeBSD.org 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 2125116A41C for ; Tue, 14 Jun 2005 02:48:05 +0000 (GMT) (envelope-from mi@aldan.algebra.com) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB48C43D48 for ; Tue, 14 Jun 2005 02:48:04 +0000 (GMT) (envelope-from mi@aldan.algebra.com) Received: (qmail 27446 invoked from network); 14 Jun 2005 02:48:04 -0000 Received: from aldan.algebra.com ([216.254.65.224]) (envelope-sender ) by mail28.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 14 Jun 2005 02:48:03 -0000 Received: from vaio.virtual-estates.net ([199.1.76.10]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j5E2lxiM024857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 13 Jun 2005 22:48:00 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Received: from vaio.virtual-estates.net (localhost [127.0.0.1]) by vaio.virtual-estates.net (8.13.3/8.13.3) with ESMTP id j5E2g311000873; Mon, 13 Jun 2005 22:42:03 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by vaio.virtual-estates.net (8.13.3/8.13.3/Submit) id j5E2g2tM000872; Mon, 13 Jun 2005 22:42:02 -0400 (EDT) (envelope-from mi@aldan.algebra.com) X-Authentication-Warning: vaio.virtual-estates.net: mi set sender to mi@aldan.algebra.com using -f From: "Mikhail T." To: George Rhoten , freebsd-threads@FreeBSD.org Date: Mon, 13 Jun 2005 22:42:01 -0400 User-Agent: KMail/1.8 References: <200506132133.j5DLXv6f045514@corbulon.video-collage.com> In-Reply-To: <200506132133.j5DLXv6f045514@corbulon.video-collage.com> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<=?utf-8?q?kcG=5EEOVihy+z3/UR=7B6SCQ=0A?= MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506132242.02124@Misha> Cc: Subject: Re: IntlTest hangs on FreeBSD (TestThreadedIntl) (PR#1141) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2005 02:48:05 -0000 = This is reproducable on the sourceforge.net NetBSD machine by executing the following: = = My initial guess is that it seems to be an OS thread scheduler bug. = The main process spins in a loop without sleeping and frequently locks = the global mutex while waiting for the other threads to finish. None = of the other threads get enough time because they are all waiting for = the global mutex lock from the main process thread when its their = turn. The main process thread is hoging the global mutex while it's in = its loop. It's not a deadlock, it's just a type of thread scheduling = that doesn't happen on other operating systems. Whether it is a bug or a legal oddity, our threads (CC-ed) people would love to hear about it... = Adding a sleep() or a yield statement in the main thread of the test = allows the test to finish. The fix will be available in ICU 3.4. -mi From owner-freebsd-threads@FreeBSD.ORG Wed Jun 15 09:16:03 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 4A54116A41F for ; Wed, 15 Jun 2005 09:16:03 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36F2443D49; Wed, 15 Jun 2005 09:16:03 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5F9G0IB021041; Wed, 15 Jun 2005 09:16:01 GMT (envelope-from davidxu@freebsd.org) Message-ID: <42AFF243.9080908@freebsd.org> Date: Wed, 15 Jun 2005 17:17:55 +0800 From: David Xu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050319 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mi@aldan.algebra.com, grhoten@jtcsv.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-threads@freebsd.org Subject: Re: IntlTest hangs on FreeBSD (TestThreadedIntl) (PR#1141) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 09:16:03 -0000 Have you tried it with libthr on -CURRENT ? David Xu -----Original Message----- From: owner-freebsd-threads@freebsd.org [mailto:owner-freebsd-threads@freebsd.org]On Behalf Of Mikhail T. Sent: 2005年6月14日 10:42 To: George Rhoten; freebsd-threads@FreeBSD.org Subject: Re: IntlTest hangs on FreeBSD (TestThreadedIntl) (PR#1141) = This is reproducable on the sourceforge.net NetBSD machine by executing the following: = = My initial guess is that it seems to be an OS thread scheduler bug. = The main process spins in a loop without sleeping and frequently locks = the global mutex while waiting for the other threads to finish. None = of the other threads get enough time because they are all waiting for = the global mutex lock from the main process thread when its their = turn. The main process thread is hoging the global mutex while it's in = its loop. It's not a deadlock, it's just a type of thread scheduling = that doesn't happen on other operating systems. Whether it is a bug or a legal oddity, our threads (CC-ed) people would love to hear about it... = Adding a sleep() or a yield statement in the main thread of the test = allows the test to finish. The fix will be available in ICU 3.4. -mi _______________________________________________ freebsd-threads@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-threads To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" From owner-freebsd-threads@FreeBSD.ORG Wed Jun 15 11:27:40 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 D8DAE16A41F for ; Wed, 15 Jun 2005 11:27:40 +0000 (GMT) (envelope-from mi@aldan.algebra.com) Received: from mail24.sea5.speakeasy.net (mail24.sea5.speakeasy.net [69.17.117.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E69943D53 for ; Wed, 15 Jun 2005 11:27:40 +0000 (GMT) (envelope-from mi@aldan.algebra.com) Received: (qmail 6642 invoked from network); 15 Jun 2005 11:27:39 -0000 Received: from aldan.algebra.com ([216.254.65.224]) (envelope-sender ) by mail24.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 15 Jun 2005 11:27:39 -0000 Received: from vaio.virtual-estates.net ([199.1.76.10]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j5FBRXeM029916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Jun 2005 07:27:36 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Received: from vaio.virtual-estates.net (localhost [127.0.0.1]) by vaio.virtual-estates.net (8.13.3/8.13.3) with ESMTP id j5FBRPw4005304; Wed, 15 Jun 2005 07:27:25 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by vaio.virtual-estates.net (8.13.3/8.13.3/Submit) id j5FBRN1Y005303; Wed, 15 Jun 2005 07:27:23 -0400 (EDT) (envelope-from mi@aldan.algebra.com) X-Authentication-Warning: vaio.virtual-estates.net: mi set sender to mi@aldan.algebra.com using -f From: "Mikhail T." To: David Xu Date: Wed, 15 Jun 2005 07:27:22 -0400 User-Agent: KMail/1.8 References: <42AFF243.9080908@freebsd.org> In-Reply-To: <42AFF243.9080908@freebsd.org> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<=?utf-8?q?kcG=5EEOVihy+z3/UR=7B6SCQ=0A?= MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506150727.23486@Misha> Cc: freebsd-threads@freebsd.org, grhoten@jtcsv.com Subject: Re: IntlTest hangs on FreeBSD (TestThreadedIntl) (PR#1141) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2005 11:27:41 -0000 = Have you tried it with libthr on -CURRENT ? No, not in a while. The bug is not 100% reproducible either. You can try it for yourself: cd /usr/ports/devel/icu make make intltest Yours, -mi = = My initial guess is that it seems to be an OS thread scheduler bug. = = The main process spins in a loop without sleeping and frequently = = locks the global mutex while waiting for the other threads to = = finish. None of the other threads get enough time because they are = = all waiting for the global mutex lock from the main process thread = = when its their turn. The main process thread is hoging the global = = mutex while it's in its loop. It's not a deadlock, it's just a type = = of thread scheduling that doesn't happen on other operating systems. = = Whether it is a bug or a legal oddity, our threads (CC-ed) people = would love to hear about it... = = = Adding a sleep() or a yield statement in the main thread of the test = = allows the test to finish. The fix will be available in ICU 3.4. = = -mi From owner-freebsd-threads@FreeBSD.ORG Thu Jun 16 10:09:54 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 33BA116A41C for ; Thu, 16 Jun 2005 10:09:54 +0000 (GMT) (envelope-from ant@emict.com) Received: from mail.emict.com (brig.emict.com [212.90.172.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E24C443D1F for ; Thu, 16 Jun 2005 10:09:53 +0000 (GMT) (envelope-from ant@emict.com) Received: from [10.0.0.232] (unknown [10.0.0.232]) by mail.emict.com (Postfix) with ESMTP id CD40644668 for ; Thu, 16 Jun 2005 13:09:51 +0300 (EEST) From: Andriy Tkachuk Organization: eMICT To: freebsd-threads@freebsd.org Date: Thu, 16 Jun 2005 13:09:51 +0300 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506161309.51431.ant@emict.com> Subject: more than 2k threads with -lpthread or -lthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 10:09:54 -0000 Hi folks. I have troubles with network threaded application wich uses several thousands threads with libthr or libpthread in RELENG_5_x. Program is killed by sigsegv. libc_r works but application eats more cpu with it. The program is the load test client application to the server. It simulates clients to the server. Each client is one thread in it. Thereby i have a question: is anybody use such kind of application with libpthread or libthr? If yes, then do you make some system tunings in order to force your application be working? Tanks, Andriy Tkachuk. From owner-freebsd-threads@FreeBSD.ORG Thu Jun 16 10:52:33 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 BB5E516A41F for ; Thu, 16 Jun 2005 10:52:33 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3C8243D49; Thu, 16 Jun 2005 10:52:33 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5GAqUfT050666; Thu, 16 Jun 2005 10:52:32 GMT (envelope-from davidxu@freebsd.org) Message-ID: <42B159E4.8080501@freebsd.org> Date: Thu, 16 Jun 2005 18:52:20 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.8) Gecko/20050605 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andriy Tkachuk References: <200506161309.51431.ant@emict.com> In-Reply-To: <200506161309.51431.ant@emict.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: more than 2k threads with -lpthread or -lthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 10:52:33 -0000 Andriy Tkachuk wrote: >Hi folks. > >I have troubles with network threaded application >wich uses several thousands threads with libthr or libpthread >in RELENG_5_x. Program is killed by sigsegv. >libc_r works but application eats more cpu with it. > >The program is the load test client application to the >server. It simulates clients to the server. Each >client is one thread in it. > >Thereby i have a question: is anybody use >such kind of application with libpthread or libthr? >If yes, then do you make some system tunings in order >to force your application be working? > >Tanks, > Andriy Tkachuk. > > > Both libpthread and libthr use 1M bytes stack on 32bits platform and 2M bytes stack on 64bits platform. I think 2k threads needs 2G stack on i386, this is too large. David Xu From owner-freebsd-threads@FreeBSD.ORG Thu Jun 16 14:18:59 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 AFBCD16A41C; Thu, 16 Jun 2005 14:18:59 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7408C43D49; Thu, 16 Jun 2005 14:18:58 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id CE6F41F0DD; Thu, 16 Jun 2005 16:18:57 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id AE9E8654F; Thu, 16 Jun 2005 16:18:57 +0200 (CEST) Date: Thu, 16 Jun 2005 16:18:57 +0200 From: Marc Olzheim To: David Xu Message-ID: <20050616141857.GA63602@stack.nl> References: <200506161309.51431.ant@emict.com> <42B159E4.8080501@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <42B159E4.8080501@freebsd.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Andriy Tkachuk , freebsd-threads@freebsd.org Subject: Re: more than 2k threads with -lpthread or -lthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 14:18:59 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jun 16, 2005 at 06:52:20PM +0800, David Xu wrote: > Both libpthread and libthr use 1M bytes stack on 32bits platform > and 2M bytes stack on 64bits platform. I think 2k threads needs > 2G stack on i386, this is too large. In which case pthread_attr_setstacksize() might help ? Marc --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCsYpRezjnobFOgrERApNuAKCZTR7MHo1jbvavXtAgttwdbv2rwgCfRbe3 hX/mus8eMQiIWZjZ9xXh4XE= =UIM9 -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-threads@FreeBSD.ORG Thu Jun 16 21:50:24 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 489DD16A41C for ; Thu, 16 Jun 2005 21:50:24 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 355F043D1D; Thu, 16 Jun 2005 21:50:24 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5GLoMXt039738; Thu, 16 Jun 2005 21:50:23 GMT (envelope-from davidxu@freebsd.org) Message-ID: <42B1F414.9040203@freebsd.org> Date: Fri, 17 Jun 2005 05:50:12 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.8) Gecko/20050605 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marc Olzheim References: <200506161309.51431.ant@emict.com> <42B159E4.8080501@freebsd.org> <20050616141857.GA63602@stack.nl> In-Reply-To: <20050616141857.GA63602@stack.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Andriy Tkachuk , freebsd-threads@freebsd.org Subject: Re: more than 2k threads with -lpthread or -lthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 21:50:24 -0000 Marc Olzheim wrote: >On Thu, Jun 16, 2005 at 06:52:20PM +0800, David Xu wrote: > > >>Both libpthread and libthr use 1M bytes stack on 32bits platform >>and 2M bytes stack on 64bits platform. I think 2k threads needs >>2G stack on i386, this is too large. >> >> > >In which case pthread_attr_setstacksize() might help ? > >Marc > > pthread_attr_setstacksize definitively helps, libc_r default uses 64k stack for thread, this is very small stack. Here two sysctl also have to tuned to numbers larger than 2000 for libthr and libpthread: kern.threads.max_groups_per_proc kern.threads.max_threads_per_proc David Xu From owner-freebsd-threads@FreeBSD.ORG Fri Jun 17 10:17:28 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 708AC16A41C; Fri, 17 Jun 2005 10:17:28 +0000 (GMT) (envelope-from ant@emict.com) Received: from mail.emict.com (brig.emict.com [212.90.172.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0023C43D53; Fri, 17 Jun 2005 10:17:27 +0000 (GMT) (envelope-from ant@emict.com) Received: from [10.0.0.232] (unknown [10.0.0.232]) by mail.emict.com (Postfix) with ESMTP id 29A8133ED1; Fri, 17 Jun 2005 13:17:26 +0300 (EEST) From: Andriy Tkachuk Organization: eMICT To: David Xu Date: Fri, 17 Jun 2005 13:17:23 +0300 User-Agent: KMail/1.8 References: <200506161309.51431.ant@emict.com> <20050616141857.GA63602@stack.nl> <42B1F414.9040203@freebsd.org> In-Reply-To: <42B1F414.9040203@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506171317.24632.ant@emict.com> Cc: Marc Olzheim , freebsd-threads@freebsd.org Subject: Re: more than 2k threads with -lpthread or -lthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2005 10:17:28 -0000 thank you guys, all started working. actually the problem with sigsegv was not about stack size - my fault - program was killed with this signal even when number of threads was not large. on 5.4-STABLE Fri Jun 17 09:33:54 EEST 2005 kernel this problem disappeared. Note, that with old kernel (from 5.4-RELEASE) but with new libpthread (from 5.4-STABLE) the problem still was present, that's why i untimely sayd that this bug present in RELENG_5_x. So i suppose, that something in 5.4-STABLE kernel is fixed regarding threads compared to 5.4-RELEASE kernel. after this another problem appeared - no more, than 30xx threads where started. But i set stacksize to 2 pages (8K) and all started working fine. Again: sorry for misinformation and thank you for help. Regards, Andriy Tkachuk. On Friday 17 June 2005 00:50, David Xu wrote: > Marc Olzheim wrote: > > >On Thu, Jun 16, 2005 at 06:52:20PM +0800, David Xu wrote: > > > > > >>Both libpthread and libthr use 1M bytes stack on 32bits platform > >>and 2M bytes stack on 64bits platform. I think 2k threads needs > >>2G stack on i386, this is too large. > >> > >> > > > >In which case pthread_attr_setstacksize() might help ? > > > >Marc > > > > > pthread_attr_setstacksize definitively helps, libc_r default uses 64k > stack for thread, this is very small stack. > > Here two sysctl also have to tuned to numbers larger than 2000 for > libthr and libpthread: > kern.threads.max_groups_per_proc > kern.threads.max_threads_per_proc > > David Xu > > From owner-freebsd-threads@FreeBSD.ORG Fri Jun 17 10:59:05 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 2EFFC16A41C; Fri, 17 Jun 2005 10:59:05 +0000 (GMT) (envelope-from ant@emict.com) Received: from mail.emict.com (brig.emict.com [212.90.172.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id BADE743D58; Fri, 17 Jun 2005 10:59:04 +0000 (GMT) (envelope-from ant@emict.com) Received: from [10.0.0.232] (unknown [10.0.0.232]) by mail.emict.com (Postfix) with ESMTP id D08B93408F; Fri, 17 Jun 2005 13:59:02 +0300 (EEST) From: Andriy Tkachuk Organization: eMICT To: David Xu Date: Fri, 17 Jun 2005 13:59:00 +0300 User-Agent: KMail/1.8 References: <200506161309.51431.ant@emict.com> <20050616141857.GA63602@stack.nl> <42B1F414.9040203@freebsd.org> In-Reply-To: <42B1F414.9040203@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506171359.01441.ant@emict.com> Cc: freebsd-threads@freebsd.org Subject: Re: more than 2k threads with -lpthread or -lthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2005 10:59:05 -0000 On Friday 17 June 2005 00:50, David Xu wrote: > Here two sysctl also have to tuned to numbers larger than 2000 for > libthr and libpthread: > kern.threads.max_groups_per_proc > kern.threads.max_threads_per_proc Also i want to note, that i didn't change this sysctls. Theirs default values are: kern.threads.max_threads_per_proc: 1500 kern.threads.max_groups_per_proc: 1500 and i make 5000 threads with -lpthread. The only sysctls i change in order to work with such number of threads are kern.maxfiles and kern.ipc.maxsockets, but they are not about threads. Regards, Andriy Tkachuk. From owner-freebsd-threads@FreeBSD.ORG Fri Jun 17 12:28:20 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 3194516A41C for ; Fri, 17 Jun 2005 12:28:20 +0000 (GMT) (envelope-from dan.cojocar@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD12043D49 for ; Fri, 17 Jun 2005 12:28:19 +0000 (GMT) (envelope-from dan.cojocar@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so1019127wri for ; Fri, 17 Jun 2005 05:28:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Y5OT9ZiZdIn5/YLMDwidMNOCWhkD4YGqOrd5rG5n0P9oTLQhoYfrB42m1zfxpC1jb3JDo12Fm5hUEAIQFSVIATJxhYRgKhzNJQKq8UYT8OJcmyVc7abK9bXNvcIDfItPjUl612yF4DQwfHB25+tQVfJxNN4qMG7An7amrhMQxXw= Received: by 10.54.51.26 with SMTP id y26mr1233758wry; Fri, 17 Jun 2005 05:28:19 -0700 (PDT) Received: by 10.54.26.12 with HTTP; Fri, 17 Jun 2005 05:28:19 -0700 (PDT) Message-ID: Date: Fri, 17 Jun 2005 15:28:19 +0300 From: Dan Cojocar To: freebsd-java@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Cc: freebsd-threads@freebsd.org Subject: Re: Fatal error: mutex is on list X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dan Cojocar List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2005 12:28:20 -0000 > I received this fatal error using jdk build > 1.5.0-p1-root_12_may_2005_13_14 with -current from Mon May 23 10:32:18 > EEST 2005: >=20 > Fatal error 'mutex is on list' at line 540 in file > /usr/src/lib/libpthread/thread/thr_mutex.c (errno =3D 0) >=20 > Here is a backtrace: > (gdb) bt > #0 0x280b0bf7 in pthread_testcancel () from /usr/lib/libpthread.so.1 > #1 0x280a03ff in sigaction () from /usr/lib/libpthread.so.1 > #2 0x2809969d in pthread_kill () from /usr/lib/libpthread.so.1 > #3 0x28098fdf in raise () from /usr/lib/libpthread.so.1 > #4 0x28198eda in abort () from /lib/libc.so.6 > #5 0x280b2781 in pthread_testcancel () from /usr/lib/libpthread.so.1 > #6 0x280a431b in _pthread_mutex_trylock () from /usr/lib/libpthread.so.1 > #7 0x280a582a in pthread_mutex_lock () from /usr/lib/libpthread.so.1 > #8 0x28532ca6 in OSThread::pd_initialize () from > /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #9 0x28532a4d in OSThread::OSThread () from > /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #10 0x2853438e in os::create_thread () from > /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #11 0x28594666 in JavaThread::JavaThread () from > /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #12 0x2848b0e6 in JVM_StartThread () from > /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so > #13 0x2b121c09 in ?? () I'm receiving again this and i'm sending this to the -threads too, maybe someone from there will notice :), Here is a new bt, they are the same untill frame #7: (gdb) bt #0 0x280b0bf7 in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x280a03ff in sigaction () from /usr/lib/libpthread.so.1 #2 0x2809969d in pthread_kill () from /usr/lib/libpthread.so.1 #3 0x28098fdf in raise () from /usr/lib/libpthread.so.1 #4 0x28198eda in abort () from /lib/libc.so.6 #5 0x280b2781 in pthread_testcancel () from /usr/lib/libpthread.so.1 #6 0x280a431b in _pthread_mutex_trylock () from /usr/lib/libpthread.so.1 #7 0x280a582a in pthread_mutex_lock () from /usr/lib/libpthread.so.1 #8 0x28532e0c in OSThread::pd_destroy () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #9 0x28532abb in OSThread::~OSThread () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #10 0x2853498d in os::free_thread () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #11 0x285923ad in Thread::~Thread () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #12 0x28594ac3 in JavaThread::~JavaThread () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #13 0x28594c3b in JavaThread::thread_main_inner () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #14 0x28594baf in JavaThread::run () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #15 0x28534059 in _start () from /usr/local/jdk1.5.0/jre/lib/i386/client/libjvm.so #16 0x2809b100 in pthread_create () from /usr/lib/libpthread.so.1 #17 0x2817ad9f in _ctx_start () from /lib/libc.so.6 Thanks, Dan From owner-freebsd-threads@FreeBSD.ORG Fri Jun 17 15:23:48 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org 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 E6C7D16A41C; Fri, 17 Jun 2005 15:23:48 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (delight.idiom.com [216.240.32.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE23543D4C; Fri, 17 Jun 2005 15:23:48 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 84A281F8A5B; Fri, 17 Jun 2005 08:23:48 -0700 (PDT) Received: from [192.168.2.5] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id j5HFNjWT007154; Fri, 17 Jun 2005 08:23:47 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <42B2EAFE.6010800@elischer.org> Date: Fri, 17 Jun 2005 08:23:42 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050424 X-Accept-Language: en, hu MIME-Version: 1.0 To: Andriy Tkachuk References: <200506161309.51431.ant@emict.com> <20050616141857.GA63602@stack.nl> <42B1F414.9040203@freebsd.org> <200506171359.01441.ant@emict.com> In-Reply-To: <200506171359.01441.ant@emict.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: David Xu , freebsd-threads@freebsd.org Subject: Re: more than 2k threads with -lpthread or -lthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2005 15:23:49 -0000 Andriy Tkachuk wrote: > On Friday 17 June 2005 00:50, David Xu wrote: > >>Here two sysctl also have to tuned to numbers larger than 2000 for >>libthr and libpthread: >>kern.threads.max_groups_per_proc >>kern.threads.max_threads_per_proc > > > Also i want to note, that i didn't change this sysctls. > Theirs default values are: > > kern.threads.max_threads_per_proc: 1500 > kern.threads.max_groups_per_proc: 1500 > > and i make 5000 threads with -lpthread. in libpthread, if threads are not in the kernel then they do not count towards these limits.. they are only in the kernel if they are waiting on a kernel resource (e.g. a file or socket etc.) in libthread all threads will count owards this limit. this is the difference between the two libraries. One tries to be more careful with kernel resources and the other is a lot simpler to get right :-) > > The only sysctls i change in order to work with such > number of threads are kern.maxfiles and kern.ipc.maxsockets, > but they are not about threads. > > Regards, > Andriy Tkachuk. > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" From owner-freebsd-threads@FreeBSD.ORG Sat Jun 18 19:58:10 2005 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B83016A41C; Sat, 18 Jun 2005 19:58:10 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8672D43D1D; Sat, 18 Jun 2005 19:58:10 +0000 (GMT) (envelope-from ceri@FreeBSD.org) Received: from freefall.freebsd.org (ceri@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j5IJwABB059982; Sat, 18 Jun 2005 19:58:10 GMT (envelope-from ceri@freefall.freebsd.org) Received: (from ceri@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j5IJwApi059977; Sat, 18 Jun 2005 19:58:10 GMT (envelope-from ceri) Date: Sat, 18 Jun 2005 19:58:10 GMT From: Ceri Davies Message-Id: <200506181958.j5IJwApi059977@freefall.freebsd.org> To: r_chipi@yahoo.com, ceri@FreeBSD.org, freebsd-threads@FreeBSD.org Cc: Subject: Re: threads/20490: Termios timeout parameters, VMIN, VTIME, dont work with lang/python X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jun 2005 19:58:10 -0000 Synopsis: Termios timeout parameters, VMIN, VTIME, dont work with lang/python State-Changed-From-To: open->closed State-Changed-By: ceri State-Changed-When: Sat Jun 18 19:56:25 GMT 2005 State-Changed-Why: Sounds fair to me. From: Daniel Eischen Message-ID: On Mon, 6 Jun 2005, Ceri Davies wrote: > Synopsis: Termios timeout parameters, VMIN, VTIME, dont work with > lang/python > > Responsible-Changed-From-To: perky->freebsd-threads > Responsible-Changed-By: ceri > Responsible-Changed-When: Mon Jun 6 21:29:37 GMT 2005 > Responsible-Changed-Why: > Seems to be a thread library problem. You might as well close this; it isn't going to be fixed. It's only a problem with libc_r. Works fine with libpthread and libthr. http://www.freebsd.org/cgi/query-pr.cgi?pr=20490