KSE/ia64: NULL thread pointer in _thr_sig_add()

Daniel Eischen eischen at vigrid.com
Sat Aug 16 16:29:14 PDT 2003


On Sat, 16 Aug 2003, Marcel Moolenaar wrote:

> On Sat, Aug 16, 2003 at 06:13:36AM -0400, Daniel Eischen wrote:
> > On Mon, 11 Aug 2003, Marcel Moolenaar wrote:
> > 
> > > On Mon, Aug 11, 2003 at 02:34:08PM +0800, David Xu wrote:
> > > > 
> > > > I have a patch trying to fix the problem, I haven't tested it,
> > > > http://people.freebsd.org/~davidxu/kse/thr_kern.c.diff
> > > > I think some calls of kse_set_curthread is bogus, Dan might need to
> > > > rethink it.
> > > 
> > > I think this is it. I now get sig 11, but it looks like a faulty
> > > use of random(). It appears random() is not thread safe and this
> > > particular test program uses random.
> > > 
> > > I'll continue to run tests, but so far it looks like the patch is
> > > fixing KSE/ia64.
> > 
> > So as of now, where do we stand for KSE on ia64?  Do ACE tests
> > pass?
> 
> Good question. I don't know. I wanted to try it at home in case I
> ran into other kernel panics, but I cannot compile.
> 
> There's at least a problem with the mutex_d test, so I suspect that
> we still have some lingering issues. This does not look to be
> related to thread pointers. I don't know to what extend it will affect
> ACE.

One question.  When you call (the syscall) setcontext() from
_ia64_break_setcontext(), do you ignore the signal mask (uc.uc_sigmask)?

-- 
Dan Eischen



More information about the freebsd-threads mailing list