This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New problems with gcc-2.8.0 based code - NOW FIXED!
- To: Manfred Hollstein <manfred at s-direktnet dot de>
- Subject: Re: New problems with gcc-2.8.0 based code - NOW FIXED!
- From: Philip Blundell <Philip dot Blundell at pobox dot com>
- Date: Tue, 30 Dec 1997 17:48:36 +0000
- cc: law at cygnus dot com, rms at gnu dot org, Manfred dot Hollstein at ks dot sel dot alcatel dot de, oliva at dcc dot unicamp dot br, gcc2 at cygnus dot com, egcs at cygnus dot com
> Dec 30 13:58:50 saturn kernel: Call Trace: [<c011b96d>] [<c011b99d>] [<c011c
>14c>] [<c0109f1a>]
Can you run this through the ksymoops decoder to get a meaningful backtrace
(with function names)?
>And so on - a lot of kernel Oops's follow. I really don't know, who's
>to blame?!?! Looking at Linux's `mm/slab.c' where the `kmem_free:..."
>messages result from, doesn't really help, as there is _NO_ loop! BUT,
More likely it's the function that calls the SLAB code that is to blame. If
you find out what that is and compile it with -S -funroll-all-loops, that
might be the way forward.
>Does anybody know an e-mail address whom we can forward these
>questions?
linux-kernel@vger.rutgers.edu is probably your best bet.
p.