Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Jun 2006 08:59:34 -0400 (EDT)
From:      Daniel Eischen <deischen@freebsd.org>
To:        Mikhail Teterin <mi+mx@aldan.algebra.com>
Cc:        threads@freebsd.org
Subject:   Re: SIGINFO and pthreads
Message-ID:  <Pine.GSO.4.64.0606080858330.4039@sea.ntplx.net>
In-Reply-To: <200606071906.25776.mi%2Bmx@aldan.algebra.com>
References:  <200606071906.25776.mi%2Bmx@aldan.algebra.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0606080858330.4039>