From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9313 invoked by alias); 21 Jan 2002 00:48:41 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 9279 invoked from network); 21 Jan 2002 00:48:36 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 21 Jan 2002 00:48:36 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id D19453F0F; Sun, 20 Jan 2002 19:48:32 -0500 (EST) Message-ID: <3C4B6560.6010201@cygnus.com> Date: Sun, 20 Jan 2002 16:48:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Per Bothner Cc: gdb-patches@sources.redhat.com Subject: Re: patch to ignore SIGPWR and SIGXCPU (used by pthreads) References: <3C49D806.4050500@bothner.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00617.txt.bz2 > Index: infrun.c > =================================================================== > RCS file: /cvs/src/src/gdb/infrun.c,v > retrieving revision 1.50 > diff -u -p -r1.50 infrun.c > --- infrun.c 2002/01/17 22:15:17 1.50 > +++ infrun.c 2002/01/19 20:17:19 > @@ -4298,6 +4298,12 @@ of the program stops.", &cmdlist); > signal_stop[TARGET_SIGNAL_WINCH] = 0; > signal_print[TARGET_SIGNAL_WINCH] = 0; > > + /* These are used for pthread context switching, used by libgcj. */ > + signal_stop[TARGET_SIGNAL_PWR] = 0; > + signal_print[TARGET_SIGNAL_PWR] = 0; > + signal_stop[TARGET_SIGNAL_XCPU] = 0; > + signal_print[TARGET_SIGNAL_XCPU] = 0; > + > /* 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 > Per, can you please expand a little on the history of this choice of signals? SIGXCPU terminate process CPU time limit exceeded (see SIGPWR discard signal power failure/restart I don't know that it is right to always silence/ignore these signals when not all systems are using pthreads/libgcj. This is even more interesting given that just below we have: /* 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. */ signal_stop[TARGET_SIGNAL_LWP] = 0; signal_print[TARGET_SIGNAL_LWP] = 0; signal_stop[TARGET_SIGNAL_WAITING] = 0; signal_print[TARGET_SIGNAL_WAITING] = 0; signal_stop[TARGET_SIGNAL_CANCEL] = 0; signal_print[TARGET_SIGNAL_CANCEL] = 0; puzzled, Andrew