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