From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-hacker-return-5776-listarch-libc-hacker=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 21817 invoked by alias); 31 Oct 2002 19:57:03 -0000
Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:libc-hacker-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/libc-hacker/>
List-Post: <mailto:libc-hacker@sources.redhat.com>
List-Help: <mailto:libc-hacker-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: libc-hacker-owner@sources.redhat.com
Received: (qmail 21777 invoked from network); 31 Oct 2002 19:57:02 -0000
Received: from unknown (HELO sccrmhc02.attbi.com) (204.127.202.62)
  by sources.redhat.com with SMTP; 31 Oct 2002 19:57:02 -0000
Received: from lucon.org ([12.234.88.146]) by sccrmhc02.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20021031195702.FOUD21167.sccrmhc02.attbi.com@lucon.org>;
          Thu, 31 Oct 2002 19:57:02 +0000
Received: by lucon.org (Postfix, from userid 1000)
	id CADD72C4EC; Thu, 31 Oct 2002 11:57:01 -0800 (PST)
Date: Thu, 31 Oct 2002 18:44:00 -0000
From: "H. J. Lu" <hjl@lucon.org>
To: Jes Sorensen <jes@trained-monkey.org>
Cc: libc-hacker@sources.redhat.com
Subject: Re: 2.2.x mips signal crash
Message-ID: <20021031115701.A20971@lucon.org>
References: <200210311950.g9VJoST18983@trained-monkey.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200210311950.g9VJoST18983@trained-monkey.org>; from jes@trained-monkey.org on Thu, Oct 31, 2002 at 02:50:28PM -0500
X-SW-Source: 2002-10/txt/msg00115.txt.bz2

On Thu, Oct 31, 2002 at 02:50:28PM -0500, Jes Sorensen wrote:
> Hi
> 
> We are chasing a problem on Linux/mips with glibc-2.2.x, which I am not
> sure whether is a kernel bug or a libc bug. We haven't been able to
> reproduce it under Linux/x86 or Linux/ia64 so far though.
> 
> Basically what seems to be happening is the following, a task is
> spawned from fork(), the child sends some signals to the parent after
> which it exits.
> 
> The parent exits before the signals arrives and a signal is delivered
> some time after reaching exit(). As the signal handler is using
> printf() we get an explosion since the file descriptor seems to be
> gone (munmap()).
> 
> My question is as follows: Is one required to wait for signal delivery
> in the parent before exiting or unregister the signal handlers? or is
> it a genuine bug?
> 
> Any suggestions?
> 

A testcase?


H.J.