[gnu.gcc.bug] possible gcc-1.34 problem

eap@BU-IT.BU.EDU (Eric A. Pearce) (04/07/89)

  I got this error when building X11R3 on a Sun4 running 4.0.1
  I did not have any problems with the code when it was compiled on
  a Sun3 running 4.0, using gcc 1.34.
 
  I don't know if it is a problem with gcc or not, but it worked when
  I used /bin/cc.

gcc -traditional -v -g -DPURDUE -O -I../. -I.././server/include    -sun4 -c  rgb.c
gcc version 1.34
 /usr/local/lib/gcc-cpp -v -DPURDUE -I../. -I.././server/include
-undef -D__GNUC__ -Dsparc -Dsun -Dunix -D__sparc__ -D__sun__
-D__unix__  -D__OPTIMIZE__ -traditional rgb.c /tmp/cca16598.cpp
GNU CPP version 1.34
 /usr/local/lib/gcc-cc1 /tmp/cca16598.cpp -quiet -dumpbase rgb.c -g -O
-traditional -version -o /tmp/cca16598.s
GNU C version 1.34 (sparc) compiled by GNU C version 1.34.
 as /tmp/cca16598.s -o rgb.o
rm -f rgb
gcc -traditional -v -g -DPURDUE -o rgb rgb.o  -O   -ldbm 
gcc version 1.34
 ld -o rgb -e start -dc -dp -Bstatic /lib/crt0.o rgb.o -ldbm 
/usr/local/lib/gcc-gnulib -lg -lc 
./rgb rgb < rgb.txt
sh: 16606 Memory fault - core dumped
*** Error code 139
make: Fatal error: Command failed for target `rgb.pag'
rgb% gdb rgb core
Program terminated with signal 11, Segmentation fault.
(gdb) where
#0  0x381c in calchash ()
(gdb)

 calchash is a function in the dbm library.  I compiled the dbm stuff
 from the 4.3 BSD source, linked it instead of using -ldbm and it
 worked fine.

 Anybody seen this before?

-------------------------------------------------------------------------------
 Eric Pearce                                   ARPANET eap@bu-it.bu.edu
 Boston University Information Technology      CSNET   eap%bu-it@bu-cs
 111 Cummington Street                         JNET    jnet%"ep@buenga" 
 Boston MA 02215                               UUCP    !harvard!bu-cs!bu-it!eap 
 617-353-2780 voice  617-353-6260 fax          BITNET  ep@buenga

rms@WHEATIES.AI.MIT.EDU (Richard Stallman) (04/07/89)

Sorry, I cannot do anything about a GCC bug without
(1) a complete self-contained input file to try, and
(2) the number of the line which is compiled incorrectly.

Can anyone else can reproduce this problem and tell me this information?