Date: Mon, 30 Jun 2003 19:03:54 -0700 (PDT) From: xiong jinshan <xiongjinshan@yahoo.com> To: deischen@freebsd.org Cc: threads@freebsd.org Subject: Re: About the kse signal process Message-ID: <20030701020354.40108.qmail@web80509.mail.yahoo.com> In-Reply-To: <Pine.GSO.4.10.10306301216050.20122-100000@pcnet5.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030701020354.40108.qmail>