Xref: utzoo gnu.g++.help:695 comp.lang.c++:12823
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!psuvax1!ukma!usenet.ins.cwru.edu!tut.cis.ohio-state.edu!unreplyable!garbage
From: caeco!integra!rwk@HELLGATE.UTAH.EDU (Richard W. Kreutzer)
Newsgroups: gnu.g++.help,comp.lang.c++
Subject: g++-1.39.0 and gdb 3.5
Message-ID: <9104120711.AA01135@noname>
Date: 12 Apr 91 07:11:52 GMT
Sender: daemon@tut.cis.ohio-state.edu
Followup-To: gnu.g++.help
Organization: Gatewayed from the GNU Project mailing list help-g++@prep.ai.mit.edu
Lines: 27

I have been without a machine for several months so this may be old stuff
but...

I installed g++-1.39.0 on a SparcStation running SunOS 4.1.1 without incident.
Next, I installed gdb-3.5 also without incident.

But when I compiled my application with g++ and tried to debug it gdb
encountered symbol table symbol type errors at every breakpoint.  I could not
debug anything compiled with g++-1.39.0 without symbol type errors!

So I backed off to g++-1.37.1 and gdb worked fine.  I am still using
g++-1.37.1 but would like to use 1.39 for several reasons.

Has anyone else had this problem?  Is there a fix?  I have not posted this as
a bug yet because I am hoping there is already a fix and I just missed it
being away from mail for so long.

Thanks

P.S., If you are using g++-1.39, how is it?  I used it only long enough to
discover my problems with gdb-3.5.  Would you recommend it over 1.37?

--
        Richard (Dick) W. Kreutzer
UUCP:   hellgate.utah.edu!caeco!integra!rwk
Mail:   Integra Software Corp.; 3995 Alpine Valley Circle; Sandy, UT 84092 (USA)
Phone:  +1(801)943-6303