Yes, I was thinking that each ThreadContext can have Signals registered
(which would mean another Class), each Signal identifies the type and
handler location perhaps.
Hans Dulimarta wrote:
>
> "Frank V. Castellucci" wrote:
> >
> > Hans,
> >
> > Saw the comment on the feature and check-ins.
> >
> > The problem I had with the signal mask on thread creation was that it
> > wasn't supported in kernel 2.2.12, was I mistaken? Does it work? <grin>
> >
>
> Does it mean that the CLONE_SIGHAND bit in the mask does not
> have any effect
> in 2.2.12? I'm using 2.2.16, so I don't know how it works in
> 2.2.12.
>
> If this approach is not supported in earlier kernel, I think
> another
> solution is to let each Thread register its handler to the
> thread manager
> (the Thread class) and when a certain signal is raised, the
> manager
> will lookup a table of registered handlers and call each of
> them.
> This table is index by signal number. However, this approach
> requires
> the manager to define handler for all possible signal
> number.
>
> > I will test it out later today and have a more detailed look.
> >
> > --
> > Frank V. Castellucci
> > http://corelinux.sourceforge.net
> > OOA/OOD/C++ Standards and Guidelines for Linux
> >
> > _______________________________________________
> > Corelinux-develop mailing list
> > Cor...@li...
> > http://lists.sourceforge.net/lists/listinfo/corelinux-develop
>
> --
> Hans Dulimarta, Ph.D. | dul...@co...
> Research Associate | http://www.egr.msu.edu/~dulimart
> P: 517-432-7589 | http://snapsource.sourceforge.net
> F: 760-281-7691 | http://corelinux.sourceforge.net
> ECE Dept. Michigan State University, E. Lansing, MI 48824
>
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/lists/listinfo/corelinux-develop
--
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package
|
