From owner-freebsd-threads@FreeBSD.ORG  Thu Nov 23 00:13:56 2006
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 <freebsd-threads@freebsd.org>; 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 <freebsd-threads@freebsd.org>; 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 <freebsd-threads@freebsd.org>; 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: <b1fa29170611221613o66fd645ct92e3ca37af42aa67@mail.gmail.com>
Date: Wed, 22 Nov 2006 16:13:52 -0800
From: "Kip Macy" <kip.macy@gmail.com>
To: "David Xu" <davidxu@freebsd.org>
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 <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=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 <davidxu@freebsd.org> 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"
>