I have taken another look into the toolchain building scripts and they
add patches to
a) glibc-jz
b) gcc
cd ${BUILD_PATH}/${GCC_VER}/libiberty
cat strsignal.c | sed -e 's/#ifndef HAVE_PSIGNAL/#if 0/g' >junk.c
cp -f strsignal.c strsignal.c.fixed; mv -f junk.c strsignal.c
b) should not have any influence since it patches -liberty which is
used by gcc itself. So it should only influence how gcc reacts on ctl-C.
a) creates a modified glibc which is used as the basis for all user-
space code. It should not have an influence on the kernel itself of
course.
This brings up one question: what makes us sure that it is indeed a
Kernel bug?
Or is simply the NPTL in the glibc broken? In that case the kernel
would correctly report a stack corruption when trying to return from
some function call.
Therefore we should run the Posix Test Suite!
http://sourceforge.net/project/showfiles.php?group_id=64592&release_id=332108
Unfortunately, I don't know if and how it can easily be adapted for
cross-compilation. Maybe the easiest way would be to get a native
toolchain to run on the 2.6 kernel (unless that one also comes with
SIGILL). And then run the test suite there.
Nikolaus
_______________________________________________
Mipsbook-devel mailing list
Mipsbook-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
