From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24996 invoked by alias); 5 Jan 2011 07:22:59 -0000 Received: (qmail 24986 invoked by uid 22791); 5 Jan 2011 07:22:58 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 05 Jan 2011 07:22:53 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id E1F042BAB90 for ; Wed, 5 Jan 2011 02:22:51 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nf89VMVitlLv for ; Wed, 5 Jan 2011 02:22:51 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 763332BAB8B for ; Wed, 5 Jan 2011 02:22:51 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 950BB145870; Wed, 5 Jan 2011 11:22:45 +0400 (RET) Date: Wed, 05 Jan 2011 07:22:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: does it make sense to stop on SIGPRIO? Message-ID: <20110105072245.GA28888@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-01/txt/msg00013.txt.bz2 I've been looking at how we decide what to when we receive a signal. We have some code that disables stop&printing for various signals because these signals are used as part of normal thread operations. /* These signals are used internally by user-level thread implementations. (See signal(5) on Solaris.) Like the above signals, a healthy program receives and handles them as part of its normal operation. */ We do the same for other signals, which are not error signals: /* Signals that are not errors should not normally enter the debugger. */ On LynxOS, changing the priority of a thread automatically causes a SIGPRIO signal to be raised. I think that SIGPRIO falls more into the second category (not a signal used to indicate an error). Are there any known situations where we would want a SIGPRIO would be indicating something abnormal, or significant enough that we would want to stop? Thanks, -- Joel