From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8560 invoked by alias); 24 Apr 2004 15:44:00 -0000 Mailing-List: contact rda-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: rda-owner@sources.redhat.com Received: (qmail 8547 invoked from network); 24 Apr 2004 15:44:00 -0000 Date: Sat, 24 Apr 2004 15:44:00 -0000 From: Daniel Jacobowitz To: Kevin Buettner Cc: rda@sources.redhat.com Subject: Re: [PATCH] Ignore realitme signals. Message-ID: <20040424154359.GA2621@nevyn.them.org> References: <20040420131308.0f8af440@saguaro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040420131308.0f8af440@saguaro> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-q2/txt/msg00003.txt.bz2 On Tue, Apr 20, 2004 at 01:13:08PM -0700, Kevin Buettner wrote: > I've just committed the patch below. > > The comment in the patch explains what it's about. I've seen this > problem (in which rda terminates due to getting a signal intended for > one of the inferior threads and terminates) in at three different > environments now (all embedded linux, but different architectures). > While I suspect that the real problem lies in the kernel, it certainly > doesn't hurt for RDA to ignore any real-time signals sent to it. > > * server.c (main): Ignore realtime signals. At least some versions of the kernel will send a child's exit signal to the debugger, instead of SIGCHLD - this should be fixed in 2.6 series kernels, but I think it was broken through all of 2.2 and 2.4. GDB had the same problem for a while, IIRC. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer