Re: Resolution (Re: [uml-devel] 2.4.22-[67] problems)

[Jeff D. <jd...@ad...>]

md...@de... said:
> It turns out that this problem seems to be due to compiler
> incompatibility. UML had been built with gcc 2.95 due to old breakage,
> and when built with gcc 3.3 (as glibc is), everything starts working
> again.  My suspicion is that this is due to certain recent changes in
> pthreads.

Is it your opinion that there's no problem in UML itself?  Having a field
in the sigcontext getting magically munged is somewhat worrying.  I'd be 
happier knowing what exactly was happening so I can be sure this wasn't
exposing some subtle UML bug.

				Jeff