From owner-freebsd-threads@FreeBSD.ORG Sun Nov 19 06:33:17 2006 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 7277916A40F for ; Sun, 19 Nov 2006 06:33:16 +0000 (UTC) (envelope-from Lycos@opticalsolutions.com) Received: from eoc8.neoplus.adsl.tpnet.pl (eoc8.neoplus.adsl.tpnet.pl [83.20.18.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C36443D70 for ; Sun, 19 Nov 2006 06:31:16 +0000 (GMT) (envelope-from Lycos@opticalsolutions.com) Message-ID: <000a01c70ba5$35956100$08121453@viper1vvuvxsrd> From: "Computer Windows" To: freebsd-threads@freebsd.org Date: Sun, 19 Nov 2006 07:37:39 +0100 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0006_01C70BAD.97529D10" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: pages NGage related forums 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, 19 Nov 2006 06:33:17 -0000 ------=_NextPart_000_0006_01C70BAD.97529D10 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable All tipscheat Core thousands of titles on major Also am. Has forum is to = discuss cheatsgame in Revolution or new tons? Number pages Ngage related = forums systemsthe Unknown Gamers in reviews! Copy Netscape Terms Usevisit our. Gaming Zone Contains some. Gamescheat Patch Includes Krypt a large collection ps. Url update listing become an editor in report in. Gamecube gba nds covering popular Features product news list. Directory = Games Video Console Platforms am Cheats and Hints. Nintendo Sega Sony Xbox. Gameshark Nintendo Sega Sony is Xbox see = alsogames of Computer Windows. Windows Aboutcom Game Strategies Offers cheat codes of Faqsthe. Xploder Site Official website range. Terms Usevisit a our sister sites mozillaorg am Chefmoz. Gigablast of = Google Lycos msn Wisenut edit this category. Ask Clusty Gigablast or = Google a. Pages or Ngage related forums systemsthe Unknown a. Find out how leave levels in like in Halo? All tipscheat Core thousands = of titles on major Also am. ------=_NextPart_000_0006_01C70BAD.97529D10-- From owner-freebsd-threads@FreeBSD.ORG Mon Nov 20 11:10:11 2006 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 5CE3D16A518 for ; Mon, 20 Nov 2006 11:10:11 +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 1E38643DE2 for ; Mon, 20 Nov 2006 11:08:15 +0000 (GMT) (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 kAKB8V6h001645 for ; Mon, 20 Nov 2006 11:08:31 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kAKB8TbI001641 for freebsd-threads@FreeBSD.org; Mon, 20 Nov 2006 11:08:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Nov 2006 11:08:29 GMT Message-Id: <200611201108.kAKB8TbI001641@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, 20 Nov 2006 11:10:11 -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/72353 threads Assertion fails in /usr/src/lib/libpthread/sys/lock.c, 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 29 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/74180 threads KSE problem. Applications those riched maximum possibl 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 10 problems total. From owner-freebsd-threads@FreeBSD.ORG Wed Nov 22 12:14:16 2006 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 12C4216A4C9 for ; Wed, 22 Nov 2006 12:14:16 +0000 (UTC) (envelope-from vaidehi.shukla@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB9B43DA6 for ; Wed, 22 Nov 2006 12:12:07 +0000 (GMT) (envelope-from vaidehi.shukla@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so491528nfc for ; Wed, 22 Nov 2006 04:12:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=eh9g3cmZ1+phZYAQaX4zwmWoh9Gp80gJje/56jm+BN8vQ010AGxoKVlerxhMyBIE3byG1wJ8RGYjVKkf2nxrAHgFxi3Ehznihp00OzAbhii9EAdsy8MyCBgmty79z6lMHIcsxatVoiGS/PoBaDTeomH5zYv6S9+gxMoM36NUo/A= Received: by 10.82.129.8 with SMTP id b8mr1212247bud.1164197553971; Wed, 22 Nov 2006 04:12:33 -0800 (PST) Received: by 10.82.127.11 with HTTP; Wed, 22 Nov 2006 04:12:33 -0800 (PST) Message-ID: <90242b1f0611220412l4ef4c92jd6f3e308f7c882fd@mail.gmail.com> Date: Wed, 22 Nov 2006 17:42:33 +0530 From: "Vaidehi Shukla" 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: gcore thread problem? 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, 22 Nov 2006 12:14:16 -0000 Hi All, 'gcore' doesn't display correct backtrace (info threads) for multi-threaded application. Is there any way to get correct backtrace (i.e. info threads) with gcore in freebsd?. Let me know if you can suggest some method to get correct backtrace. Thanks & Regards, Vaidehi From owner-freebsd-threads@FreeBSD.ORG Thu Nov 23 00:01:53 2006 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 44B5916A412; Thu, 23 Nov 2006 00:01:53 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: freebsd-threads@freebsd.org Date: Thu, 23 Nov 2006 08:01:45 +0800 User-Agent: KMail/1.8.2 References: <90242b1f0611220412l4ef4c92jd6f3e308f7c882fd@mail.gmail.com> In-Reply-To: <90242b1f0611220412l4ef4c92jd6f3e308f7c882fd@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611230801.45966.davidxu@freebsd.org> Cc: Subject: Re: gcore thread problem? 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, 23 Nov 2006 00:01:53 -0000 On Wednesday 22 November 2006 20:12, Vaidehi Shukla wrote: > Hi All, > > 'gcore' doesn't display correct backtrace (info threads) for multi-threaded > application. Is there any way to get correct backtrace (i.e. info threads) > with gcore in freebsd?. Let me know if you can suggest some method to get > correct backtrace. > > Thanks & Regards, > Vaidehi I think it becauses threaded application does not work correctly with procfs, one problem is gcore is using files in /proc to get information, if an application has thousands of thread, should kernel create so much vnode for the application ? it seems to be overkill. David Xu From owner-freebsd-threads@FreeBSD.ORG Thu Nov 23 00:13:56 2006 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 F082516A40F for ; Thu, 23 Nov 2006 00:13:55 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7965143D5C for ; Thu, 23 Nov 2006 00:13:23 +0000 (GMT) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so655946nfc for ; Wed, 22 Nov 2006 16:13:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=BDDG27fTMAAvDfjIE1BPZD8eHI0th/BmkJgD73jGqCOVGjl5Wt78Tn8o/2sh4d3naqjIEHp5+O5WMUwQYmtInJHy9a8jE3aHOwac/isFI5jh5yEKn1KY/5wmn66f2FJq8P4rBV0ra7Lt8atqWePz+0WoB1b9/NIZfC3Znau9q0c= Received: by 10.82.141.4 with SMTP id o4mr986307bud.1164240832883; Wed, 22 Nov 2006 16:13:52 -0800 (PST) Received: by 10.82.191.20 with HTTP; Wed, 22 Nov 2006 16:13:52 -0800 (PST) Message-ID: Date: Wed, 22 Nov 2006 16:13:52 -0800 From: "Kip Macy" To: "David Xu" In-Reply-To: <200611230801.45966.davidxu@freebsd.org> MIME-Version: 1.0 References: <90242b1f0611220412l4ef4c92jd6f3e308f7c882fd@mail.gmail.com> <200611230801.45966.davidxu@freebsd.org> 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 Cc: freebsd-threads@freebsd.org Subject: Re: gcore thread problem? 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, 23 Nov 2006 00:13:56 -0000 That isn't how multi-threading is handled for core-files. For each thread an additional set of GPRs and FPRs is added to the elf header. -Kip On 11/22/06, David Xu wrote: > > On Wednesday 22 November 2006 20:12, Vaidehi Shukla wrote: > > Hi All, > > > > 'gcore' doesn't display correct backtrace (info threads) for > multi-threaded > > application. Is there any way to get correct backtrace (i.e. info > threads) > > with gcore in freebsd?. Let me know if you can suggest some method to > get > > correct backtrace. > > > > Thanks & Regards, > > Vaidehi > > I think it becauses threaded application does not work correctly with > procfs, one problem is gcore is using files in /proc to get information, > if an application has thousands of thread, should kernel create so much > vnode for the application ? it seems to be overkill. > > David Xu > _______________________________________________ > 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 Thu Nov 23 00:22:03 2006 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B813116A415; Thu, 23 Nov 2006 00:22:02 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: "Kip Macy" Date: Thu, 23 Nov 2006 08:21:56 +0800 User-Agent: KMail/1.8.2 References: <90242b1f0611220412l4ef4c92jd6f3e308f7c882fd@mail.gmail.com> <200611230801.45966.davidxu@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200611230821.57012.davidxu@freebsd.org> Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: gcore thread problem? 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, 23 Nov 2006 00:22:03 -0000 On Thursday 23 November 2006 08:13, Kip Macy wrote: > That isn't how multi-threading is handled for core-files. For each thread > an additional set of GPRs and FPRs is added to the elf header. > > -Kip > I know, but procfs does not export thread information. David Xu > On 11/22/06, David Xu wrote: > > On Wednesday 22 November 2006 20:12, Vaidehi Shukla wrote: > > > Hi All, > > > > > > 'gcore' doesn't display correct backtrace (info threads) for > > > > multi-threaded > > > > > application. Is there any way to get correct backtrace (i.e. info > > > > threads) > > > > > with gcore in freebsd?. Let me know if you can suggest some method to > > > > get > > > > > correct backtrace. > > > > > > Thanks & Regards, > > > Vaidehi > > > > I think it becauses threaded application does not work correctly with > > procfs, one problem is gcore is using files in /proc to get information, > > if an application has thousands of thread, should kernel create so much > > vnode for the application ? it seems to be overkill. > > > > David Xu > > _______________________________________________ > > 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"