Date: Thu, 25 Jun 1998 18:26:22 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: J.Hogeveen@twiddle.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Signal-11 Message-ID: <199806252326.SAA07983@detlev.UUCP> In-Reply-To: <Pine.BSF.3.96.980625214302.12963A-100000@Dot.Twiddle.COM> (message from Jeroen Hogeveen on Thu, 25 Jun 1998 21:51:05 %2B0200 (CEST)) References: <Pine.BSF.3.96.980625214302.12963A-100000@Dot.Twiddle.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
> hi, just one quick question. sorry to ask it here, but response on > -questions is 0,0. > Has anyone had experiences regarding sig11's like these? > .map\" -O -pipe -I/usr/local/include log-server.c > gcc: Internal compiler error: program as got fatal signal 11 > *** Error code 1 > Sig-11 indicates a SIGSEV - segmentation violation as far as I know. > Does this mean my memory (configuration) is bad or that my CPU is > overheated? Check for reproducability. If it's easily reproducable, then it is probably a bug in gcc. These frequently will apply only to particular sequences of C statements. I would suggest finding which function the failure occours in (by using #if 0 / #endif to generate a binary search), then narrow it to a small bit of code. That code may be rewritten to avoid the bug. If you are using gcc 2.8.1, then it would be nice to send in a bug report to bug-gcc@gnu.org with the snippet of code. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806252326.SAA07983>