[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
GCC, flops(1) and signal 4
- To: tech_(_at_)_openbsd_(_dot_)_org, misc_(_at_)_openbsd_(_dot_)_org
- Subject: GCC, flops(1) and signal 4
- From: wargames <wargames_(_at_)_edmc_(_dot_)_net>
- Date: Mon, 3 Aug 1998 23:46:03 -0600 (MDT)
- Reply-to: wargames <wargames_(_at_)_edmc_(_dot_)_net>
This evening I was trying to compile the flops program as downloaded from
<ftp://ftp.nosc.mil/pub/aburto/flops/> gcc (mac68k v2.8.1) purrs along quite
nicely only bothering to complain that main doesn't return an int. Suddenly my
disklight blinks, I am told there was an 'Internal compiler error: cc1 got
fatal signal 4' and then I am rewarded with a 1MB coredump.
'man signal' told me that signal 4 was SIGILL: illegal instruction and a legit
cause to dump core. Thinking that this may be similar to the sig 11 / memory
problem, I let gcc try its hand at recompiling the kernel. no problems there.
using 'strings cc1.core | more' I found most of my preprocessed source in
memory, and later on, some stuff that looked suspiciously like assembly code
about to be output.
Anyone have any suggestions as to what's going on in gcc? Should I run cpp,
cc1, as, and ld manually so I can use a debugger to figure out what's wrong?
This is more annoying than crucial. Nothing else that I've ever tried to
compile has done this...
wargames[_(_at_)_]edmc[_(_dot_)_]net pager: 403.917.6448
http://www.edmc.net/~wargames/ ICQ 16382437 / 16383973
Visit your host, monkey.org