Path: utzoo!telly!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!UUNET.UU.NET!edsr!jupiter!cheeks
From: edsr!jupiter!cheeks@UUNET.UU.NET (Mark Costlow)
Newsgroups: gnu.g++.bug
Subject: Re:  my report about g++ vs. debugging symbols
Message-ID: <8912111921.AA00720@argon.eds.com>
Date: 11 Dec 89 19:21:57 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 16


Well, I personally haven't gotten anywhere in looking for this bug.  Although,
I have come up with a question:  A LOT of the code for cc1plus (and cc1 too,
I'm sure) seems to be made up of macros designed to access pieces of large 
structures.  This does make the code look pretty nice, but it seems to render
debugging near impossible for anybody that isn't intimately familiar with the
code.  (I suppose it could be argued that those of us who aren't intimate
with it shouldn't be meddling with it anyway :-).  So, my question is "How
do you guys debug it?"  Some tips would help.

I also really need to get the compiler up on my HPs and Sun3s, so any help
with the debugging symbols problem would be appreciated also. 

>>mark

cheeks@edsr.eds.com   or    ...!uunet!edsr!cheeks