From owner-freebsd-threads@FreeBSD.ORG Sun Mar 18 05:33:12 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5966116A400 for ; Sun, 18 Mar 2007 05:33:12 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id 326AE13C44C for ; Sun, 18 Mar 2007 05:33:11 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (b82u7f8nxchx8ena@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l2I5X90k029943; Sat, 17 Mar 2007 21:33:09 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l2I5X8aY029942; Sat, 17 Mar 2007 22:33:08 -0700 (PDT) (envelope-from jmg) Date: Sat, 17 Mar 2007 21:33:07 -0800 From: John-Mark Gurney To: Max Laier Message-ID: <20070318053307.GC73385@funkthat.com> Mail-Followup-To: Max Laier , freebsd-arch@freebsd.org, freebsd-threads@freebsd.org References: <45F906ED.8070100@aueb.gr> <200703151827.39963.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200703151827.39963.max@love2party.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-threads@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Multithreaded qsort(3) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2007 05:33:12 -0000 Max Laier wrote this message on Thu, Mar 15, 2007 at 18:27 +0100: > I'd suggest to name it qsort() and put it in a separate library (not > necessarily named libc_mt, as I don't believe there are that many > functions in libc, that can actually gain from multithreading). What happens when you attempt to link a library that uses qsort, but isn't multi-thread safe? You may be able to protect calls to the library w/ a lock, but then when it calls qsort, the library would break.. Keeping the qsort name sounds ripe for problems down the road... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-threads@FreeBSD.ORG Sun Mar 18 07:10:33 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B1E916A400 for ; Sun, 18 Mar 2007 07:10:33 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.freebsd.org (Postfix) with ESMTP id 1A16113C45A for ; Sun, 18 Mar 2007 07:10:32 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so913511wxc for ; Sun, 18 Mar 2007 00:10:32 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Uz+FQ8tUpdeyEIeEtR3jXcKIYdzp5eQp1IqzcvbeuaW0WoQyGyy+jZJQcG0wxQ6ZmhVvbqg+rylHyIncZ7d1FJnpI1uuoxaM856x0oFdOm17MxhOHy8SjGpYxmB3VRBm6PW7k4+Uh5uyIslix2WlQJoEbZ17vxtIVSeuItNMAPA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kHG2gd4oqx1f4XiWzONM4CigWPk4pEeWT5QOr8CF7xQ8KiWrBh5ubxMm3A/tqyy24sHssg2vUbtuURzX9hYIXLb+C2atw0jlB/G2WUAyGtqaf8Zfm/IaqwnibhwX8nMesR7Y/c3pBCiM4DjRGwh/g7YRqRhJf0ZTwiJWqwzwQrw= Received: by 10.90.27.15 with SMTP id a15mr3083078aga.1174200214965; Sat, 17 Mar 2007 23:43:34 -0700 (PDT) Received: by 10.90.25.1 with HTTP; Sat, 17 Mar 2007 23:43:34 -0700 (PDT) Message-ID: Date: Sat, 17 Mar 2007 23:43:34 -0700 From: "Kip Macy" To: "John-Mark Gurney" , "Max Laier" , freebsd-arch@freebsd.org, freebsd-threads@freebsd.org In-Reply-To: <20070318053307.GC73385@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45F906ED.8070100@aueb.gr> <200703151827.39963.max@love2party.net> <20070318053307.GC73385@funkthat.com> Cc: Subject: Re: Multithreaded qsort(3) 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: Sun, 18 Mar 2007 07:10:33 -0000 On 3/17/07, John-Mark Gurney wrote: > Max Laier wrote this message on Thu, Mar 15, 2007 at 18:27 +0100: > > I'd suggest to name it qsort() and put it in a separate library (not > > necessarily named libc_mt, as I don't believe there are that many > > functions in libc, that can actually gain from multithreading). > > What happens when you attempt to link a library that uses qsort, but > isn't multi-thread safe? You may be able to protect calls to the > library w/ a lock, but then when it calls qsort, the library would > break.. > > Keeping the qsort name sounds ripe for problems down the road... Reminds me of how Solaris blindly uses vfork for implementing system(3). It was very easy for a naive user (me) to call system from a multi-threaded python application. I had numerous failures that were impossible to track back to system(3). -Kip From owner-freebsd-threads@FreeBSD.ORG Sun Mar 18 19:43:13 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4E4C16A403; Sun, 18 Mar 2007 19:43:13 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 4A50913C43E; Sun, 18 Mar 2007 19:43:13 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (dialup175.ach.sch.gr [81.186.70.175]) (authenticated bits=128) by igloo.linux.gr (8.13.8/8.13.8/Debian-3) with ESMTP id l2IJW71h009603 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 18 Mar 2007 21:32:19 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.13.8/8.13.8) with ESMTP id l2IJW0eg075952; Sun, 18 Mar 2007 21:32:01 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.13.8/8.13.8/Submit) id l2IDn12A007455; Sun, 18 Mar 2007 15:49:01 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 18 Mar 2007 15:49:01 +0200 From: Giorgos Keramidas To: Kip Macy Message-ID: <20070318134900.GA98260@kobe.laptop> References: <45F906ED.8070100@aueb.gr> <200703151827.39963.max@love2party.net> <20070318053307.GC73385@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.425, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.30, BAYES_00 -2.60, DATE_IN_PAST_03_06 0.48, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Max Laier , freebsd-threads@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Multithreaded qsort(3) 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: Sun, 18 Mar 2007 19:43:14 -0000 On 2007-03-17 23:43, Kip Macy wrote: > Reminds me of how Solaris blindly uses vfork for implementing > system(3). It was very easy for a naive user (me) to call system from > a multi-threaded python application. I had numerous failures that were > impossible to track back to system(3). It seems like an 'obvious' optimization, though. vfork() will block the parent process until the child runs exec(), and the whole purpose of system is to exec() a shell and run an external command. Can you elaborate on the problems you were seeing? It sounds like something both interesting and educational :) From owner-freebsd-threads@FreeBSD.ORG Mon Mar 19 08:45:14 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 781AF16A400 for ; Mon, 19 Mar 2007 08:45:14 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id 1F09413C448 for ; Mon, 19 Mar 2007 08:45:07 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.0/8.13.8) with ESMTP id l2J8Papb087081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Mar 2007 03:25:37 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.0/8.14.0/Submit) id l2IKPF3D076302; Sun, 18 Mar 2007 15:25:15 -0500 (CDT) (envelope-from dan) Date: Sun, 18 Mar 2007 15:25:15 -0500 From: Dan Nelson To: Giorgos Keramidas Message-ID: <20070318202515.GF64778@dan.emsphone.com> References: <45F906ED.8070100@aueb.gr> <200703151827.39963.max@love2party.net> <20070318053307.GC73385@funkthat.com> <20070318134900.GA98260@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070318134900.GA98260@kobe.laptop> X-OS: FreeBSD 6.2-STABLE User-Agent: Mutt/1.5.14 (2007-02-12) Cc: freebsd-threads@freebsd.org, freebsd-arch@freebsd.org, Max Laier Subject: Re: Multithreaded qsort(3) 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, 19 Mar 2007 08:45:14 -0000 In the last episode (Mar 18), Giorgos Keramidas said: > On 2007-03-17 23:43, Kip Macy wrote: > > Reminds me of how Solaris blindly uses vfork for implementing > > system(3). It was very easy for a naive user (me) to call system > > from a multi-threaded python application. I had numerous failures > > that were impossible to track back to system(3). > > It seems like an 'obvious' optimization, though. vfork() will block > the parent process until the child runs exec(), and the whole purpose > of system is to exec() a shell and run an external command. > > Can you elaborate on the problems you were seeing? It sounds like > something both interesting and educational :) Btw - the Solaris 10 system manpage only mentions signal interactions as the cause for MT-unsafeness: "The system() function manipulates the signal handlers for SIGINT, SIGQUIT, and SIGCHLD. It is therefore not safe to call system() in a multithreaded process, since some other thread that manipulates these signal handlers and a thread that concurrently calls system() can interfere with each other in a destructive manner. If, however, no such other thread is active, system() can safely be called concurrently from multiple threads. See popen(3C) for an alternative to system() that is thread-safe." It looks like there were some vfork-related system() bugs in older versions of Solaris, but they appear to have been fixed: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4332595 -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-threads@FreeBSD.ORG Mon Mar 19 11:08:44 2007 Return-Path: X-Original-To: freebsd-threads@FreeBSD.org Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E92A416A402 for ; Mon, 19 Mar 2007 11:08:43 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id C99A913C46A for ; Mon, 19 Mar 2007 11:08:43 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2JB8hZf055605 for ; Mon, 19 Mar 2007 11:08:43 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2JB8gEo055601 for freebsd-threads@FreeBSD.org; Mon, 19 Mar 2007 11:08:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Mar 2007 11:08:42 GMT Message-Id: <200703191108.l2JB8gEo055601@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon 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, 19 Mar 2007 11:08:44 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s threa/76690 threads fork hang in child for -lc_r 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/20016 threads pthreads: Cannot set scheduling timer/Cannot set virtu s threa/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket o s threa/24632 threads libc_r delicate deviation from libc in handling SIGCHL s bin/32295 threads pthread dont dequeue signals s threa/34536 threads accept() blocks other threads o kern/38549 threads the procces compiled whith pthread stopped in pthread_ s threa/39922 threads [threads] [patch] Threaded applications executed with s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under s threa/49087 threads Signals lost in programs linked with libc_r s kern/64313 threads FreeBSD (OpenBSD) pthread implicit set/unset O_NONBLOC o threa/70975 threads unexpected and unreliable behaviour when using SYSV se o threa/72429 threads threads blocked in stdio (fgets, etc) are not cancella o threa/72953 threads fork() unblocks blocked signals w/o PTHREAD_SCOPE_SYST o threa/75273 threads FBSD 5.3 libpthread (KSE) bug o threa/75374 threads pthread_kill() ignores SA_SIGINFO flag s threa/76694 threads fork cause hang in dup()/close() function in child (-l o threa/79683 threads svctcp_create() fails if multiple threads call at the o threa/80435 threads panic on high loads o threa/83914 threads [libc] popen() doesn't work in static threaded program s threa/84483 threads problems with devel/nspr and -lc_r on 4.x o threa/85160 threads [libthr] [patch] libobjc + libpthread/libthr crash pro o threa/90278 threads libthr, ULE and -current produces >100% WCPU with apac o kern/91266 threads [threads] Trying sleep, but thread marked as sleeping s threa/94467 threads send(), sendto() and sendmsg() are not correct in libc f threa/98256 threads gnome-system-monitor core dumps from pthread_testcance s threa/100815 threads FBSD 5.5 broke nanosleep in libc_r o threa/101323 threads fork(2) in threaded programs broken. o threa/103975 threads Implicit loading/unloading of libpthread.so may crash 28 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/19247 threads uthread_sigaction.c does not do anything wrt SA_NOCLDW s kern/22190 threads A threaded read(2) from a socketpair(2) fd can sometim s threa/30464 threads pthread mutex attributes -- pshared s threa/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwrite() need wra s threa/40671 threads pthread_cancel doesn't remove thread from condition qu s threa/69020 threads pthreads library leaks _gc_mutex o threa/79887 threads [patch] freopen() isn't thread-safe o threa/80992 threads abort() sometimes not caught by gdb depending on threa o threa/81534 threads [libc_r] [patch] libc_r close() will fail on any fd ty o threa/110306 threads apache 2.0 segmentation violation when calling gethost 10 problems total. From owner-freebsd-threads@FreeBSD.ORG Mon Mar 19 21:05:55 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88E2916A401; Mon, 19 Mar 2007 21:05:55 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id E41E613C45D; Mon, 19 Mar 2007 21:05:54 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.8/8.13.8/Debian-3) with ESMTP id l2JL4r6Z002957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Mar 2007 23:05:00 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.13.8/8.13.8) with ESMTP id l2JL4Z7i011407; Mon, 19 Mar 2007 23:04:47 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.13.8/8.13.8/Submit) id l2JL4Y3g011382; Mon, 19 Mar 2007 23:04:34 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 19 Mar 2007 23:04:34 +0200 From: Giorgos Keramidas To: Dan Nelson Message-ID: <20070319210434.GA7312@kobe.laptop> References: <45F906ED.8070100@aueb.gr> <200703151827.39963.max@love2party.net> <20070318053307.GC73385@funkthat.com> <20070318134900.GA98260@kobe.laptop> <20070318202515.GF64778@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070318202515.GF64778@dan.emsphone.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.507, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.69, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Max Laier , freebsd-arch@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Multithreaded qsort(3) 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, 19 Mar 2007 21:05:55 -0000 On 2007-03-18 15:25, Dan Nelson wrote: >In the last episode (Mar 18), Giorgos Keramidas said: >>On 2007-03-17 23:43, Kip Macy wrote: >>> Reminds me of how Solaris blindly uses vfork for implementing >>> system(3). It was very easy for a naive user (me) to call system >>> from a multi-threaded python application. I had numerous failures >>> that were impossible to track back to system(3). >> >> It seems like an 'obvious' optimization, though. vfork() will block >> the parent process until the child runs exec(), and the whole purpose >> of system is to exec() a shell and run an external command. >> >> Can you elaborate on the problems you were seeing? It sounds like >> something both interesting and educational :) > > Btw - the Solaris 10 system manpage only mentions signal interactions > as the cause for MT-unsafeness: > > "The system() function manipulates the signal handlers for SIGINT, > SIGQUIT, and SIGCHLD. It is therefore not safe to call system() > in a multithreaded process, since some other thread that > manipulates these signal handlers and a thread that concurrently > calls system() can interfere with each other in a destructive > manner. If, however, no such other thread is active, system() can > safely be called concurrently from multiple threads. See > popen(3C) for an alternative to system() that is thread-safe." > > It looks like there were some vfork-related system() bugs in older > versions of Solaris, but they appear to have been fixed: > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4332595 Thanks! The bug description was a very good read. The interaction with the runtime linker didn't occur to me, but now I see :) From owner-freebsd-threads@FreeBSD.ORG Wed Mar 21 09:32:30 2007 Return-Path: X-Original-To: threads@freebsd.org Delivered-To: freebsd-threads@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B435F16A40E for ; Wed, 21 Mar 2007 09:32:30 +0000 (UTC) (envelope-from bbw@integralsys.com) Received: from host-64-234-36-52.nctv.com (host-64-234-36-52.nctv.com [64.234.36.52]) by mx1.freebsd.org (Postfix) with SMTP id 070DC13C48A for ; Wed, 21 Mar 2007 09:32:29 +0000 (UTC) (envelope-from bbw@integralsys.com) Received: from [143.169.67.239] (helo=bpwigu) by host-64-234-36-52.nctv.com with smtp (Exim 4.62 (FreeBSD)) id 1HTyBi-0003UL-OZ; Wed, 21 Mar 2007 02:37:02 -0800 Message-ID: <460109BA.5060203@goosu.com> Date: Wed, 21 Mar 2007 02:32:26 -0800 From: Lucero L. Sophy User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: threads@freebsd.org Content-Type: multipart/related; boundary="------------040705010809080609080606" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: legal-size sane 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, 21 Mar 2007 09:32:30 -0000 --------------040705010809080609080606 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" outage It was a waste of time, useless, undesirable movie that just isn't worth seeing. Great for getting that document to someone without physically delivering it. Gotta run - it'll increase my score! It's a very tasty red you'll probably have some trouble stopping drinking, plus it has a nice little frog on the label. One "host" system can be controlled through web interfaces from various other machines (Windows, Mac, XBox 360, PSP, Razer (all cells? well lets just say I felt anger. One "host" system can be controlled through web interfaces from various other machines (Windows, Mac, XBox 360, PSP, Razer (all cells? but it's memory remains. 5 million in interest off that last stamp. if you actually manage to get one out of the post office. It's also nice to see that 20 minutes here, 20 minutes there all add up over the day. This movie focuses on an arranged wedding, and life in general in India. As if I couldn't buy 10 not in a book (heaven forbid! A fitness point roughly translates into a calorie, while an activity point allows you to compare your exercise to anyone else on the site. Hopefully we'll see something concrete about it in the not to distant future. The premise is fairly original, the story's good (based on a Michael Crichton book), the action, situations, and history are all believable. Apparently frogs are very susceptible to environmental damage. You like the characters, which I found to be well developed (surprising). I know I'll take flack for it - but I liked it. Sit back and enjoy the ride on this one. I couldn't get a 10 pack (they didn't have) so I had to take a 12 pack. You like the characters, which I found to be well developed (surprising). You just don't want it to end. Don't expect anything but fun from this movie - sit down and enjoy. Hopefully we'll see something concrete about it in the not to distant future. FitOff allows you to track your daily exercise, awarding Fitness and Activity points based on how long and what you did. You just don't want it to end. Hacking Email: 99 Email Security and Productivity Tips entries: 580 :: last entry: 9. com [gnabgib] bizwarcho Main Articles Blogs Books Movies Links Files Authors RSS Truths Adults have Learned Raising teenages is like nailing Jello to a tree. If you cna find it you really should try it. Apparently frogs are very susceptible to environmental damage. com [gnabgib] bizwarcho Main Articles Blogs Books Movies Links Files Authors RSS New Words for 2003 404 Someone who's clueless. or better yet just the 4 I need for now (since I'll be lining up again anyway). I guess I'm kind of hoping that people's interest wanes a little so I can get ahead - that's probably wrong of me isn't it? It's very easy drinking - I'm talking a case easy drinking. Sit back and enjoy the ride on this one. I guess I'm kind of hoping that people's interest wanes a little so I can get ahead - that's probably wrong of me isn't it? --------------040705010809080609080606-- From owner-freebsd-threads@FreeBSD.ORG Wed Mar 21 18:20:06 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3B7E416A47F for ; Wed, 21 Mar 2007 18:20:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B175613C4F8 for ; Wed, 21 Mar 2007 18:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2LIK3ON047866 for ; Wed, 21 Mar 2007 18:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2LIK3lh047865; Wed, 21 Mar 2007 18:20:03 GMT (envelope-from gnats) Resent-Date: Wed, 21 Mar 2007 18:20:03 GMT Resent-Message-Id: <200703211820.l2LIK3lh047865@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-threads@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Mikhail Modin Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7E25516A405 for ; Wed, 21 Mar 2007 18:11:11 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id 6F06A13C484 for ; Wed, 21 Mar 2007 18:11:11 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l2LIBBO0089846 for ; Wed, 21 Mar 2007 18:11:11 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l2LI6AN3087714; Wed, 21 Mar 2007 18:06:10 GMT (envelope-from nobody) Message-Id: <200703211806.l2LI6AN3087714@www.freebsd.org> Date: Wed, 21 Mar 2007 18:06:10 GMT From: Mikhail Modin To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: threads/110636: using gdb with multi thread application with lib libpthread 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, 21 Mar 2007 18:20:06 -0000 >Number: 110636 >Category: threads >Synopsis: using gdb with multi thread application with lib libpthread >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-threads >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Mar 21 18:20:03 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Mikhail Modin >Release: FreeBSD 5.5 >Organization: Kaspersky Lab >Environment: FreeBSD some.hostname 5.5-RELEASE FreeBSD 5.5-RELEASE #0: Tue May 23 14:58:27 UTC 2006 root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: It`s imposable analyze core dump files from multi thread application linked with libpthread. For example, we have application with have 4 threads. 3 of them are in runnable state, one of them generate SIGSEGV. How do I can detect it thread? #0 0x280e1373 in pthread_testcancel () from /usr/lib/libpthread.so.1 (gdb) i threads * 6 LWP 100066 0x280e1373 in pthread_testcancel () from /usr/lib/libpthread.so.1 5 Thread 5 (sleeping) 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 4 Thread 4 (LWP 100142) 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 3 Thread 3 (runnable) 0x280f70d4 in sin () from /lib/libm.so.3 2 Thread 2 (runnable) f (f=0x0) at thread_sigsegv_test.cpp:23 1 Thread 1 (runnable) 0x280f70d2 in sin () from /lib/libm.so.3 (gdb) t 5 [Switching to thread 5 (Thread 5 (sleeping))]#0 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 (gdb) bt #0 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #1 0x280d9195 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #2 0x280cc7b2 in pthread_join () from /usr/lib/libpthread.so.1 #3 0x0806127c in main () at thread_sigsegv_test.cpp:39 (gdb) t 4 [Switching to thread 4 (Thread 4 (LWP 100142))]#0 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 (gdb) bt #0 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x280d992e in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #2 0x00000000 in ?? () (gdb) >How-To-Repeat: It`s very easy. :) >Fix: I don`t know. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-threads@FreeBSD.ORG Wed Mar 21 18:20:06 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44C4D16A480 for ; Wed, 21 Mar 2007 18:20:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id EF8A813C480 for ; Wed, 21 Mar 2007 18:20:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2LIK46c047918 for ; Wed, 21 Mar 2007 18:20:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2LIK4EI047915; Wed, 21 Mar 2007 18:20:04 GMT (envelope-from gnats) Resent-Date: Wed, 21 Mar 2007 18:20:04 GMT Resent-Message-Id: <200703211820.l2LIK4EI047915@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-threads@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Mikhail Modin Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C662816A403 for ; Wed, 21 Mar 2007 18:15:19 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id B7E1A13C4BA for ; Wed, 21 Mar 2007 18:15:19 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l2LIFJ42091535 for ; Wed, 21 Mar 2007 18:15:19 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l2LIAHVE089305; Wed, 21 Mar 2007 18:10:17 GMT (envelope-from nobody) Message-Id: <200703211810.l2LIAHVE089305@www.freebsd.org> Date: Wed, 21 Mar 2007 18:10:17 GMT From: Mikhail Modin To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: threads/110637: Kaspersky Lab 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, 21 Mar 2007 18:20:06 -0000 >Number: 110637 >Category: threads >Synopsis: Kaspersky Lab >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-threads >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Mar 21 18:20:03 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Mikhail Modin >Release: FreeBSD 5.5 >Organization: Kaspersky Lab >Environment: FreeBSD some.hostname 5.5-RELEASE FreeBSD 5.5-RELEASE #0: Tue May 23 14:58:27 UTC 2006 root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: It`s imposable analyze core dump files from multi thread application linked with libpthread. For example, we have application with have 4 threads. 3 of them are in runnable state, one of them generate SIGSEGV. How do I can detect it thread? #0 0x280e1373 in pthread_testcancel () from /usr/lib/libpthread.so.1 (gdb) i threads * 6 LWP 100066 0x280e1373 in pthread_testcancel () from /usr/lib/libpthread.so.1 5 Thread 5 (sleeping) 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 4 Thread 4 (LWP 100142) 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 3 Thread 3 (runnable) 0x280f70d4 in sin () from /lib/libm.so.3 2 Thread 2 (runnable) f (f=0x0) at thread_sigsegv_test.cpp:23 1 Thread 1 (runnable) 0x280f70d2 in sin () from /lib/libm.so.3 (gdb) t 5 [Switching to thread 5 (Thread 5 (sleeping))]#0 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 (gdb) bt #0 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #1 0x280d9195 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #2 0x280cc7b2 in pthread_join () from /usr/lib/libpthread.so.1 #3 0x0806127c in main () at thread_sigsegv_test.cpp:39 (gdb) t 4 [Switching to thread 4 (Thread 4 (LWP 100142))]#0 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 (gdb) bt #0 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x280d992e in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #2 0x00000000 in ?? () (gdb) >How-To-Repeat: It`s very easy. :) >Fix: I don`t know. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-threads@FreeBSD.ORG Wed Mar 21 18:40:40 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A94EB16A419; Wed, 21 Mar 2007 18:40:40 +0000 (UTC) (envelope-from maxim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 80C5213C45E; Wed, 21 Mar 2007 18:40:40 +0000 (UTC) (envelope-from maxim@FreeBSD.org) Received: from freefall.freebsd.org (maxim@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2LIee9c051721; Wed, 21 Mar 2007 18:40:40 GMT (envelope-from maxim@freefall.freebsd.org) Received: (from maxim@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2LIeead051717; Wed, 21 Mar 2007 18:40:40 GMT (envelope-from maxim) Date: Wed, 21 Mar 2007 18:40:40 GMT From: Maxim Konovalov Message-Id: <200703211840.l2LIeead051717@freefall.freebsd.org> To: Mihail.Modin@kaspersky.com, maxim@FreeBSD.org, freebsd-threads@FreeBSD.org Cc: Subject: Re: threads/110637: Kaspersky Lab 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, 21 Mar 2007 18:40:40 -0000 Synopsis: Kaspersky Lab State-Changed-From-To: open->closed State-Changed-By: maxim State-Changed-When: Wed Mar 21 18:40:09 UTC 2007 State-Changed-Why: Duplicate of threads/110636. http://www.freebsd.org/cgi/query-pr.cgi?pr=110637 From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 07:50:04 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3937A16A50B for ; Thu, 22 Mar 2007 07:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 0302913C4D1 for ; Thu, 22 Mar 2007 07:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2M7o3Q7063640 for ; Thu, 22 Mar 2007 07:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2M7o3sk063638; Thu, 22 Mar 2007 07:50:03 GMT (envelope-from gnats) Resent-Date: Thu, 22 Mar 2007 07:50:03 GMT Resent-Message-Id: <200703220750.l2M7o3sk063638@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-threads@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Mikhail Modin Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B480816A480 for ; Thu, 22 Mar 2007 07:48:31 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id A3E6213C4D5 for ; Thu, 22 Mar 2007 07:48:31 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l2M7mTbq022325 for ; Thu, 22 Mar 2007 07:48:29 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l2M7hS6A020159; Thu, 22 Mar 2007 07:43:28 GMT (envelope-from nobody) Message-Id: <200703220743.l2M7hS6A020159@www.freebsd.org> Date: Thu, 22 Mar 2007 07:43:28 GMT From: Mikhail Modin To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: threads/110664: using gdb with multi thread application with lib libpthread 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, 22 Mar 2007 07:50:04 -0000 >Number: 110664 >Category: threads >Synopsis: using gdb with multi thread application with lib libpthread >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-threads >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Mar 22 07:50:03 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Mikhail Modin >Release: FreeBSD 5.5 >Organization: Kaspersky Lab >Environment: FreeBSD some.hostname 5.5-RELEASE FreeBSD 5.5-RELEASE #0: Tue May 23 14:58:27 UTC 2006 root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: It`s imposable analyze core dump files from multi thread application linked with libpthread. For example, we have application with have 4 threads. 3 of them are in runnable state, one of them generate SIGSEGV. How do I can detect it thread? #0 0x280e1373 in pthread_testcancel () from /usr/lib/libpthread.so.1 (gdb) i threads * 6 LWP 100066 0x280e1373 in pthread_testcancel () from /usr/lib/libpthread.so.1 5 Thread 5 (sleeping) 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 4 Thread 4 (LWP 100142) 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 3 Thread 3 (runnable) 0x280f70d4 in sin () from /lib/libm.so.3 2 Thread 2 (runnable) f (f=0x0) at thread_sigsegv_test.cpp:23 1 Thread 1 (runnable) 0x280f70d2 in sin () from /lib/libm.so.3 (gdb) t 5 [Switching to thread 5 (Thread 5 (sleeping))]#0 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 (gdb) bt #0 0x280d9233 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #1 0x280d9195 in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #2 0x280cc7b2 in pthread_join () from /usr/lib/libpthread.so.1 #3 0x0806127c in main () at thread_sigsegv_test.cpp:39 (gdb) t 4 [Switching to thread 4 (Thread 4 (LWP 100142))]#0 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 (gdb) bt #0 0x280e1353 in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x280d992e in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #2 0x00000000 in ?? () (gdb) >How-To-Repeat: It`s very easy. :) >Fix: I don`t know. ;) >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 09:35:04 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A4F6E16A50A for ; Thu, 22 Mar 2007 09:35:04 +0000 (UTC) (envelope-from girish.motwani@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.249]) by mx1.freebsd.org (Postfix) with ESMTP id 5B98B13C4D0 for ; Thu, 22 Mar 2007 09:35:04 +0000 (UTC) (envelope-from girish.motwani@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so667553ana for ; Thu, 22 Mar 2007 02:35:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=r6N+khT73alN7pXwFyJ8hoSRCa6y39LfYqsbyXmfko80ego30KUdU7TlFMBxqQr8ByL7R8SYijWjIgiSCVWHnZ+cyVJRnbM5tjo5JBMcW1rb3bGWoi8pVJ6N73S5gGwKEc6mi2sDmb7kn+munhnHj+VYg+aAFmysjBJ7+7BVlNY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=EGWZCRtlgb20i7B5ArxKVaUi4jNsrIzM6V11GM9lSkvKYL0ta9/mrDtggofkXOiO+mkUuFFGvmF7KByBWojuNLWVOsM3ZRgGAMVsosfeBqGKWIAyP6If9eZ35aQisEScuxLR47wOpRNGx09aLNg8wBs91UQnCeQoMjZiNov8a18= Received: by 10.115.107.1 with SMTP id j1mr520533wam.1174554638273; Thu, 22 Mar 2007 02:10:38 -0700 (PDT) Received: by 10.114.180.16 with HTTP; Thu, 22 Mar 2007 02:10:38 -0700 (PDT) Message-ID: <2779e6080703220210u321522c7l40cf8555cfdc2404@mail.gmail.com> Date: Thu, 22 Mar 2007 14:40:38 +0530 From: "Girish Motwani" To: freebsd-threads@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: lipthread and TLS 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, 22 Mar 2007 09:35:04 -0000 Hi, I am working on freebsd libpthread support for MIPS. Is thread local storage support (TLS) a pre-requisite for this, or the kse implementation can work without TLS ? -- Thanks, girish From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 11:04:51 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D7CE016A403 for ; Thu, 22 Mar 2007 11:04:51 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from gateway.cybervisiontech.com.ua (gateway.cybervisiontech.com.ua [88.81.251.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5644E13C483 for ; Thu, 22 Mar 2007 11:04:48 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (hq.cybervisiontech.com [127.0.0.1]) by gateway.cybervisiontech.com.ua (Postfix) with ESMTP id 6B45FED4FD8; Thu, 22 Mar 2007 12:40:28 +0200 (EET) X-Virus-Scanned: amavisd-new at cybervisiontech.com Received: from gateway.cybervisiontech.com.ua ([127.0.0.1]) by localhost (hq.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnYOjfhcQpUf; Thu, 22 Mar 2007 12:40:23 +0200 (EET) Received: from [10.2.1.87] (rein.cybervisiontech.com.ua [10.2.1.87]) by gateway.cybervisiontech.com.ua (Postfix) with ESMTP id A6093ED4FD3; Thu, 22 Mar 2007 12:40:23 +0200 (EET) Message-ID: <46025D19.6020007@icyb.net.ua> Date: Thu, 22 Mar 2007 12:40:25 +0200 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.10 (X11/20070315) MIME-Version: 1.0 To: bug-followup@FreeBSD.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: amd64/110655: 32 bit threaded applications crash on amd64 SMP kernel. 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, 22 Mar 2007 11:04:51 -0000 I can confirm this problem for 6.2-RELEASE-p2 amd64 UP system, for both libpthread and libthr. i386 simple test programs die with the following symptoms: [libpthread] program dies with sigsegv. What's interesting, when run under ktrace my very short program sometimes completes successfully and sometime crashes with the same symptoms. There is one strange line in ktrace: 66443 thr_test CALL kse_create(0x804b50c,0x1) 66443 thr_test RET kse_create 0 66443 thr_test CALL __sysctl(0xffffd7b8,0x2,0xffffd7c0,0xffffd7b4,0x2809c63c,0x18) 66443 thr_test RET __sysctl 0 66443 thr_test CALL __sysctl(0xffffd7c0,0x3,0xffffd86c,0xffffd870,0,0) 66443 thr_test RET __sysctl 0 66443 thr_test CALL break(0x805c000) 66443 thr_test RET break 0 66443 thr_test CALL mmap(0xffbfc000,0x101000,0x3,0x400,0xffffffff,0,0,0) 66443 thr_test RET mmap -4210688/0xffbfc000 66443 thr_test CALL mprotect(0xffbfc000,0x1000,0) 66443 thr_test RET mprotect 0 66443 thr_test CALL clock_gettime(0,0x8051f5c) 66443 thr_test RET clock_gettime 0 66443 thr_test CALL fstat(0x1,0xffcfc7c0) 66443 thr_test RET fstat 0 ================= 66443 thr_test RET fork 0 ================= 66443 thr_test PSIG SIGSEGV SIG_DFL 66443 thr_test NAMI "thr_test.core" [libthr] the problem here seems to be more obvious, but unexpected (at least for me): 69654 thr_test CALL sysarch(0xa,0xffffd700) 69654 thr_test RET sysarch 0 69654 thr_test CALL sigprocmask(0x3,0xffffd730,0xffffd720) 69654 thr_test RET sigprocmask 0 69654 thr_test CALL sigaction(0x20,0xffffd6d0,0) 69654 thr_test RET sigaction 0 69654 thr_test CALL sigprocmask(0x3,0xffffd720,0) 69654 thr_test RET sigprocmask 0 69654 thr_test CALL sigprocmask(0x1,0x28070a20,0xffffd760) 69654 thr_test RET sigprocmask 0 69654 thr_test CALL sigprocmask(0x3,0x28070a30,0) 69654 thr_test RET sigprocmask 0 69654 thr_test CALL _umtx_op 69654 thr_test RET _umtx_op -1 errno 78 Function not implemented 69654 thr_test PSIG SIGSYS SIG_DFL 69654 thr_test NAMI "thr_test.core" -- Andriy Gapon From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 16:45:03 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E1CF16A403 for ; Thu, 22 Mar 2007 16:45:03 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outS.internet-mail-service.net (outS.internet-mail-service.net [216.240.47.242]) by mx1.freebsd.org (Postfix) with ESMTP id 5C9C913C45D for ; Thu, 22 Mar 2007 16:45:03 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Thu, 22 Mar 2007 09:16:52 -0700 Received: from [192.168.2.4] (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 4234E125AE6; Thu, 22 Mar 2007 09:45:02 -0700 (PDT) Message-ID: <4602B28C.1020204@elischer.org> Date: Thu, 22 Mar 2007 09:45:00 -0700 From: Julian Elischer User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Girish Motwani References: <2779e6080703220210u321522c7l40cf8555cfdc2404@mail.gmail.com> In-Reply-To: <2779e6080703220210u321522c7l40cf8555cfdc2404@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: lipthread and TLS 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, 22 Mar 2007 16:45:03 -0000 Girish Motwani wrote: > Hi, > I am working on freebsd libpthread support for MIPS. Is thread local > storage support (TLS) a pre-requisite for this, or the kse implementation > can work without TLS ? > well one shouls support TLS.. does the TLS document give information for MIPS? From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 17:14:47 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E22F16A409 for ; Thu, 22 Mar 2007 17:14:47 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0476413C4C3 for ; Thu, 22 Mar 2007 17:14:46 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.14.0/8.14.0/NETPLEX) with ESMTP id l2MHEiE9021302; Thu, 22 Mar 2007 13:14:44 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.ntplx.net [204.213.176.10]); Thu, 22 Mar 2007 13:14:44 -0400 (EDT) Date: Thu, 22 Mar 2007 13:14:44 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Julian Elischer In-Reply-To: <4602B28C.1020204@elischer.org> Message-ID: References: <2779e6080703220210u321522c7l40cf8555cfdc2404@mail.gmail.com> <4602B28C.1020204@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-threads@freebsd.org Subject: Re: lipthread and TLS X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2007 17:14:47 -0000 On Thu, 22 Mar 2007, Julian Elischer wrote: > Girish Motwani wrote: >> Hi, >> I am working on freebsd libpthread support for MIPS. Is thread local >> storage support (TLS) a pre-requisite for this, or the kse implementation >> can work without TLS ? >> > > well one shouls support TLS.. does the TLS document give information for > MIPS? The toolchain itself should support TLS, so that's probably the place to look, as well as src/libexec/rtld-elf/. The libpthread library does not use TLS itself, and I don't think anything (yet) uses TLS in libc or in our base system, though I could be wrong. -- DE From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 18:14:34 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AE8B016A47B for ; Thu, 22 Mar 2007 18:14:34 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 7545813C468 for ; Thu, 22 Mar 2007 18:14:34 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.14.0/8.14.0/NETPLEX) with ESMTP id l2MIEXjo007023; Thu, 22 Mar 2007 14:14:33 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.ntplx.net [204.213.176.10]); Thu, 22 Mar 2007 14:14:33 -0400 (EDT) Date: Thu, 22 Mar 2007 14:14:33 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jason Evans In-Reply-To: <4602C49D.3080109@frebsd.org> Message-ID: References: <2779e6080703220210u321522c7l40cf8555cfdc2404@mail.gmail.com> <4602B28C.1020204@elischer.org> <4602C49D.3080109@frebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-threads@freebsd.org Subject: Re: lipthread and TLS X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2007 18:14:34 -0000 On Thu, 22 Mar 2007, Jason Evans wrote: > Daniel Eischen wrote: >> The toolchain itself should support TLS, so that's probably >> the place to look, as well as src/libexec/rtld-elf/. The >> libpthread library does not use TLS itself, and I don't >> think anything (yet) uses TLS in libc or in our base system, >> though I could be wrong. > > malloc uses TLS. Well, I stand corrected then. If you need to get MIPS up and running without TLS, you may need to hack malloc() and anything else that uses TLS to temporarily use pthread_[gs]etspecific()... -- DE From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 18:19:49 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 918CA16A40E for ; Thu, 22 Mar 2007 18:19:49 +0000 (UTC) (envelope-from jasone@frebsd.org) Received: from canonware.com (24-38-119-150-st.losaca.adelphia.net [24.38.119.150]) by mx1.freebsd.org (Postfix) with ESMTP id 778F013C448 for ; Thu, 22 Mar 2007 18:19:49 +0000 (UTC) (envelope-from jasone@frebsd.org) Received: from [10.0.0.2] (24-38-119-150-st.losaca.adelphia.net [24.38.119.150]) by canonware.com (Postfix) with ESMTP id 022171298D9; Thu, 22 Mar 2007 11:02:21 -0700 (PDT) Message-ID: <4602C49D.3080109@frebsd.org> Date: Thu, 22 Mar 2007 11:02:05 -0700 From: Jason Evans User-Agent: Thunderbird 1.5.0.10 (X11/20070302) MIME-Version: 1.0 To: Daniel Eischen References: <2779e6080703220210u321522c7l40cf8555cfdc2404@mail.gmail.com> <4602B28C.1020204@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: lipthread and TLS 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, 22 Mar 2007 18:19:49 -0000 Daniel Eischen wrote: > The toolchain itself should support TLS, so that's probably > the place to look, as well as src/libexec/rtld-elf/. The > libpthread library does not use TLS itself, and I don't > think anything (yet) uses TLS in libc or in our base system, > though I could be wrong. malloc uses TLS. Jason From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 18:24:54 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D0F216A406 for ; Thu, 22 Mar 2007 18:24:54 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.freebsd.org (Postfix) with ESMTP id B97CF13C4C8 for ; Thu, 22 Mar 2007 18:24:53 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so832102wxc for ; Thu, 22 Mar 2007 11:24:53 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fLNCHimhHBkBMgUB5OdJVXFIrITQJSGYWwD+VSfop8vWDj6Zp9P/G5OXApIMO/+muQz3q169KovuiVG42zILL+BXunaIck1jvJqKxa+shf/vSnAujUW4or7GrhbA1Bg8vyVxegS1Ux4eahCl7GzqpdC/kD3wSkbbdEQU/X0CBvo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JtFxRjv313aC0MswSe3iuFlpFkL3oqy1hJK7DFMpQzK0YELionu+NQ2E6pkKcVewyoZcNcdx2xAdlNztZE8Rd8GBvWxlFFKm6g4y6P5OP0cMesMahvqu7qd/ixkiAu9feZkexDRJxe13TTMyDrvY/UlOiYPTo0RIbDwdwbUIsXc= Received: by 10.90.84.17 with SMTP id h17mr4013710agb.1174587892652; Thu, 22 Mar 2007 11:24:52 -0700 (PDT) Received: by 10.90.116.6 with HTTP; Thu, 22 Mar 2007 11:24:52 -0700 (PDT) Message-ID: Date: Thu, 22 Mar 2007 11:24:52 -0700 From: "Kip Macy" To: "Daniel Eischen" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2779e6080703220210u321522c7l40cf8555cfdc2404@mail.gmail.com> <4602B28C.1020204@elischer.org> <4602C49D.3080109@frebsd.org> Cc: Jason Evans , freebsd-threads@freebsd.org Subject: Re: lipthread and TLS 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, 22 Mar 2007 18:24:54 -0000 On 3/22/07, Daniel Eischen wrote: > On Thu, 22 Mar 2007, Jason Evans wrote: > > > Daniel Eischen wrote: > >> The toolchain itself should support TLS, so that's probably > >> the place to look, as well as src/libexec/rtld-elf/. The > >> libpthread library does not use TLS itself, and I don't > >> think anything (yet) uses TLS in libc or in our base system, > >> though I could be wrong. > > > > malloc uses TLS. > > Well, I stand corrected then. If you need to get MIPS up > and running without TLS, you may need to hack malloc() > and anything else that uses TLS to temporarily use > pthread_[gs]etspecific()... You won't be able to use TLS unless: a) initialization works in libc - it was broken on sparc64 until recently for both static and dynamic linking b) your linker supports it - the current binutils is very much out of date, users needing it will have to build a private toolchain From owner-freebsd-threads@FreeBSD.ORG Thu Mar 22 20:00:48 2007 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 [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1AA9216A402; Thu, 22 Mar 2007 20:00:48 +0000 (UTC) (envelope-from maxim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id E434013C48C; Thu, 22 Mar 2007 20:00:47 +0000 (UTC) (envelope-from maxim@FreeBSD.org) Received: from freefall.freebsd.org (maxim@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2MK0lSe085940; Thu, 22 Mar 2007 20:00:47 GMT (envelope-from maxim@freefall.freebsd.org) Received: (from maxim@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2MK0kkZ085936; Thu, 22 Mar 2007 20:00:46 GMT (envelope-from maxim) Date: Thu, 22 Mar 2007 20:00:46 GMT From: Maxim Konovalov Message-Id: <200703222000.l2MK0kkZ085936@freefall.freebsd.org> To: Mihail.Modin@kaspersky.com, maxim@FreeBSD.org, freebsd-threads@FreeBSD.org Cc: Subject: Re: threads/110664: using gdb with multi thread application with lib libpthread 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, 22 Mar 2007 20:00:48 -0000 Synopsis: using gdb with multi thread application with lib libpthread State-Changed-From-To: open->closed State-Changed-By: maxim State-Changed-When: Thu Mar 22 19:59:56 UTC 2007 State-Changed-Why: Dup of threads/110636. gNATS: Enter the reason for changing this PR's state here. http://www.freebsd.org/cgi/query-pr.cgi?pr=110664