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: Jeffrey A Law <law at cygnus dot com>
- Date: Mon, 29 Dec 1997 11:16:37 -0700
- cc: 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
- Reply-To: law at cygnus dot com
In message <199712291737.SAA07160@saturn.s-direktnet.de>you write:
> Well, it wasn't a failure of the compiler! The kernel and all the modules
> could be built successfully, but when booting this kernel some system
> calls issued by the two programs `isapnp' and `clock' reproducably fail,
> i.e. cause `segmentation violations' of the two programs.
OK. That points to either a code generation bug or a bug in the linux
source.
> I then recompiled isapnp and clock with gcc-2.8.0 and now the situation
> became even worse: no more SIGSEGV's but kernel oops's!
:(
> Perhaps I should look at the source of the particular programs and find
> out using strace what's really going on.
Might be helpful. Though I suspect it's a kernel module that's being
mis-compiled or is incorrectly written, so the strace might tell us
what syscall is failing.
jeff