Date: Thu, 8 Jun 2006 07:40:09 +0400 (MSD) From: Maxim Konovalov <maxim@macomnet.ru> To: Mikhail Teterin <mi+mx@aldan.algebra.com> Cc: threads@freebsd.org Subject: Re: SIGINFO and pthreads Message-ID: <20060608073336.C6097@mp2.macomnet.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
Hi, On Wed, 7 Jun 2006, 19:06-0400, 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! libpthread uses SIGINFO for dumping thread information to a file but looking over the code it seems it does allow to use SIGINFO to the app. Are you sure your signal handling is correct? Signal handling in pthreads programs is tricky, e.g. all threads share signal actions but each thread has a separate signal mask. -- Maxim Konovalov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060608073336.C6097>