From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6912 invoked by alias); 5 Jan 2011 18:26:09 -0000 Received: (qmail 6897 invoked by uid 22791); 5 Jan 2011 18:26:08 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 05 Jan 2011 18:26:05 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id CBDC913075; Wed, 5 Jan 2011 10:26:03 -0800 (PST) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id BC952C9E36; Wed, 5 Jan 2011 10:26:03 -0800 (PST) Message-ID: <4D24B7BB.9040609@vmware.com> Date: Wed, 05 Jan 2011 18:26:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20101201) MIME-Version: 1.0 To: Joel Brobecker CC: "gdb@sourceware.org" Subject: Re: does it make sense to stop on SIGPRIO? References: <20110105072245.GA28888@adacore.com> <4D24B717.1060405@vmware.com> In-Reply-To: <4D24B717.1060405@vmware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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/msg00021.txt.bz2 Michael Snyder wrote: > Joel Brobecker wrote: >> 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, > > > I think it might be peculiar to LynxOS. Most google hits either refer > to gdb or Lynx. > > Meant to imply -- in which case you can do what you like. ;-)