🚀 go-pugleaf

   I have never had any problems with my favorite compiler until now. I just
updated my workstation from gcc 2.4.3.1, which was completely stable, to 
gcc 2.4.5, which hasn't worked yet. It compiles fine, and it runs "hello
world" fine, but when I try to run the program I'm currently writing it 
coredumps BEFORE the program starts to execute! I suspect that the problem
is related to the fact that I had to use the --with-gnu-as and --with-gnu-ld
options to configure, because it wouldn't assemble using the built-in as and
ld. It complained about an illegal floating-point op (I think it was 'li.d').

   gdb chokes on the gcc-generated code. Here is a sample:
(gdb) file mc
Reading symbols from mc...done.
(gdb) r
Starting program: /disk4/hofmann/mc/mc
(Internal error: pc 0x4001c0 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4001c0 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4001d4 in read in psymtab, but not in symtab.)
warning: Hit heuristic-fence-post without finding
warning: enclosing function for pc 0x4001d4
(Internal error: pc 0x4001d4 in read in psymtab, but not in symtab.)

Program received signal 11, Segmentation fault
(Internal error: pc 0x4001d4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4001d4 in read in psymtab, but not in symtab.)
(Internal error: pc 0x4001d4 in read in psymtab, but not in symtab.)
0x4001d4 in __istart ()
(Internal error: pc 0x4001d4 in read in psymtab, but not in symtab.)
(gdb) 

   Can someone please tell me what's going on!!??! Thanks,

                                                          scott
-- 

-------------------------------------------------------------------------------
J. Scott Hofmann                        | "This is fun?"
hofmann@cs.uiuc.edu                     |   -Dr. McCoy, _Star Trek VI:
                                        |             The Undiscovered Country_