About the kse signal process

[xiong jinshan]

--- Daniel Eischen <eischen at vigrid.com> wrote:
> On Mon, 30 Jun 2003, xiong jinshan wrote:
> > --- Daniel Eischen <eischen at 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