From owner-freebsd-threads@FreeBSD.ORG Thu Jun 8 14:56:56 2006 Return-Path: X-Original-To: threads@freebsd.org Delivered-To: freebsd-threads@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5141C16ABCF for ; Thu, 8 Jun 2006 12:59:50 +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 E813D43D46 for ; Thu, 8 Jun 2006 12:59:49 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k58CxYG7012512; Thu, 8 Jun 2006 08:59:34 -0400 (EDT) Date: Thu, 8 Jun 2006 08:59:34 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Mikhail Teterin In-Reply-To: <200606071906.25776.mi+mx@aldan.algebra.com> Message-ID: References: <200606071906.25776.mi+mx@aldan.algebra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: threads@freebsd.org Subject: Re: SIGINFO and pthreads 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, 08 Jun 2006 14:56:57 -0000 On Wed, 7 Jun 2006, Mikhail Teterin wrote: > Hello! > > I have a program, which updates the user with its status upon receiving a > SIGINFO (like dump, cp, dd, and fsck do). The exact same handler is installed > for SIGUSR1 (TclX does not know about SIGINFO and I needed to a Tcl script to > interact with the program too). > > When I made the program multi-threaded, it stopped reacting to the SIGINFO. It > still reacts to the SIGUSR1, but completele ignores SIGINFO now... > > If I disable the multi-threading, SIGINFO is processed again... > > What's special about SIGINFO and pthreads? Thanks! Look in /tmp. In -current, dumping of threads is only enabled when LIBPTHREAD_DEBUG is set in the environment. -- DE