Am 14.04.2009 um 12:25 schrieb ard:
On Tue, Apr 14, 2009 at 11:15:42AM +0200, Dr. H. Nikolaus Schaller
wrote:
This brings up one question: what makes us sure that it is indeed a
Kernel bug?
Well, research of Nils did point to something.
Yes, it is always the same handler for SIGILL. I.e.
On Tue, Apr 14, 2009 at 11:15:42AM +0200, Dr. H. Nikolaus Schaller wrote:
> This brings up one question: what makes us sure that it is indeed a
> Kernel bug?
Well, research of Nils did point to something.
But no, as far as I know, there is no clear case if it's user or
kernel space.
It's at leas
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
