From owner-freebsd-threads@FreeBSD.ORG Thu Dec 11 22:00:41 2008 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21CAC106564A; Thu, 11 Dec 2008 22:00:41 +0000 (UTC) (envelope-from dixit@netapp.com) Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by mx1.freebsd.org (Postfix) with ESMTP id 098EA8FC23; Thu, 11 Dec 2008 22:00:41 +0000 (UTC) (envelope-from dixit@netapp.com) X-IronPort-AV: E=Sophos;i="4.36,207,1228118400"; d="scan'208";a="96962321" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 11 Dec 2008 13:32:20 -0800 Received: from dixit-lxp.nane.netapp.com (mthorpe2-lxp.hq.netapp.com [10.97.16.108] (may be forged)) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id mBBLWJ0O000811; Thu, 11 Dec 2008 13:32:20 -0800 (PST) Message-ID: <494186E3.2010307@netapp.com> Date: Thu, 11 Dec 2008 16:32:19 -0500 From: Amol Dixit User-Agent: Thunderbird 2.0.0.18 (X11/20081105) MIME-Version: 1.0 To: Julian Elischer References: 488A213F.70105@netapp.com <48C06F77.6000006@elischer.org> <48C0923F.6080608@freebsd.org> <48C094B8.3050302@elischer.org> <48C0961E.5000300@elischer.org> In-Reply-To: <48C0961E.5000300@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: David Xu , freebsd-threads@freebsd.org Subject: stop thread on creation 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, 11 Dec 2008 22:00:41 -0000 Hi, In linux, new threads STOP before executing the first instruction of their entry routine when process is being traced. This doesn't seem to be the case with new threads on freebsd. Is there a way to make this happen from libthr/libpthread calls or any other means? Does freebsd native gdb expect new threads (from pthread_create()) to STOP so that it can resume them immediately? Thanks, Amol