> Jonathan Kinsey <address@hidden> wrote on 23/06/2009
> > I've checked in a fix, it was caused by the realigned stack pointer
> > threads (which gcc doesn't align), looks like it needs to be
> aligned at the
> > end of the function (at least this works for me).
> > It's quite likely that the threads get aligned coincidently on
> > windows systems.
> Doesn't fix the issue for me :( :( No change.
Minor: in multithread.c there's no line that shows
the revision number, like