This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
egcs woes
- To: egcs at cygnus dot com
- Subject: egcs woes
- From: Paul Tomblin <ptomblin at xcski dot com>
- Date: Mon, 25 May 1998 08:44:11 -0400
I run RedHat Linux 5.0 on a DEC Alpha "UDB" system. I installed a
pre-compiled egcs 1.0.2 rpm that I got out of the RedHat "contrib" ftp site.
When I attemped to compile the latest "qt" using it, I got several C++ files
that would not compile unless I turned off optimization. Then I compiled
Mozilla with the alpha patches and with the qtscape patches, and qtscape
would not run - it would immediately core dump. I cleaned both qt and
mozilla, and remade with standard gcc, and it ran (after a fashion). So I
took the hint and got rid of 1.0.2. When 1.0.3a came out, I installed the
source and built it myself. Now I can compile qt without any outside
intervention - optimizaton seems to work on all the c++ files. However,
when I compile qtscape, it still immediately core dumps. The console shows
the message:
qtscape-export: memory violation at pc=0039fa40 rp=155558bc10c (bad address = 0039fa40)
An attempt to look at the backtrace in gdb returns:
Cannot access memory at address 0xfffffffffffffffd.
Any suggestions?