From owner-freebsd-threads@FreeBSD.ORG  Mon Jun 30 19:03:56 2003
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E643C37B401
	for <threads@freebsd.org>; Mon, 30 Jun 2003 19:03:56 -0700 (PDT)
Received: from web80509.mail.yahoo.com (web80509.mail.yahoo.com
	[66.218.79.79])	by mx1.FreeBSD.org (Postfix) with SMTP id 42DED43FEC
	for <threads@freebsd.org>; Mon, 30 Jun 2003 19:03:54 -0700 (PDT)
	(envelope-from xiongjinshan@yahoo.com)
Message-ID: <20030701020354.40108.qmail@web80509.mail.yahoo.com>
Received: from [218.79.98.26] by web80509.mail.yahoo.com via HTTP;
	Mon, 30 Jun 2003 19:03:54 PDT
Date: Mon, 30 Jun 2003 19:03:54 -0700 (PDT)
From: xiong jinshan <xiongjinshan@yahoo.com>
To: deischen@freebsd.org
In-Reply-To: <Pine.GSO.4.10.10306301216050.20122-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: threads@freebsd.org
Subject: Re: About the kse signal process
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jul 2003 02:03:57 -0000


--- Daniel Eischen <eischen@vigrid.com> wrote:
> On Mon, 30 Jun 2003, xiong jinshan wrote:
> > --- Daniel Eischen <eischen@vigrid.com> wrote:
> > > On Mon, 30 Jun 2003, xiong jinshan wrote:
> > > 
> > > > Hi,
> > > >   I am wondering that the following piece of
> code
> > > > can't work with the unix semantics. I tested
> it
> > > with
> > > > 5.1 release and i386 arch. By unix sementics,
> if I
> > > > send the SIGALRM to this running programme, it
> > > should
> > > > be received by the thr_func() only, and print
> a
> > > prompt
> > > > msg on the console.
> > > 
> > > Yes, only thr_func() should receive the alarm.
> > This is the issue. Nothing printed on the console
> when
> > I sent the signal SIGALRM, it meant that none of
> the
> > thread received this signal.
> 
> It works for me with both libc_r and libkse.  This
> is from
> a very recent -current.  I can't test under
> 5.1-release.
> There have been some changes lately with regard to
> signals
> in -current and libkse.  I don't know about
> libc_r...
It received the SIGSEGV before the main() when I
linked   with libc_r;(.

> 
> --
> Dan Eischen
> 


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com