🚀 go-pugleaf

From:	MX%"youngdale@v6550c.nrl.navy.mil"   13-AUG-1992 11:45:21.72
To:	MUNROE
CC:	
Subj:	RE: Bug in GAS inhibits DEBUGger functioning.

Return-Path: <youngdale@v6550c.nrl.navy.mil>
Received: by DMC.COM (MX V3.1C) with UUCP; Thu, 13 Aug 1992 11:45:13 EDT
Received: from V6550C.NRL.NAVY.MIL by relay1.UU.NET with SMTP
          (5.61/UUNET-internet-primary) id AA03823; Thu, 13 Aug 92 10:50:56
          -0400
Received: by v6550c.nrl.navy.mil (MX V2.3) id 11338; Thu, 13 Aug 1992 10:50:40
          EDT
Date: Thu, 13 Aug 1992 10:50:40 EDT
From: Eric Youngdale <youngdale@v6550c.nrl.navy.mil>
To: munroe@DMC.COM
CC: youngdale@v6550c.nrl.navy.mil
Message-ID: <0095F07E.AF5952E0.11338@v6550c.nrl.navy.mil>
Subject: RE: Bug in GAS inhibits DEBUGger functioning.


>garning(debugger output):Forward reference error, dbx type 66
>gcc-as warning(debugger output):Forward reference error, dbx type 71
>gcc-as warning(debugger output):Unable to resolve 1 circular references.

	OK, I have looked at the problem, and the core issue is that the
compiler is generating incomplete debugging information.  In particular,
the declaration:

.stabs "K560_R_TRACKING_DATA:T73=u10
	k560_t_asCharacter:74=ar1;0;9;11,0,80;
	k560_r_asReply:75=ar1;0;1;76,0,80;
	k560_r_asDevices:77,0,80;;",128,0,0,0

references an array in k560_r_asReply of dbx type 76, and dbx type 76
is not defined anywhere in the file.  This is what is responsible for
the unresolved circular reference.  The other two messages, about dbx
types 66 and 71 represent similar situations, where a dbx type is
used, but not defined.  In these two cases the references are such
that the assembler can work around the problem, but the circular
reference really throws the assembler off.

	The reason that I am giving this to you is that I would like you to
make a bug report to the mailing list bug-g++@prep.ai.mit.edu (it appears
to be g++ code), and you will need to supply source code and my explanation
of what the trouble it.

	In the mean time, I will try to come up with a patch to the
assembler that will make it more fault tolerant.  In this situation, I
will fix it so that structure elements of undefined dbx types will not
be visible from the debugger.

	I also want to mention that I am about to go away for a week,
and I may not get back to this for a little while.  I hope that you
can find a work-around in the mean time.

-Eric

--
Dick Munroe				Internet: munroe@dmc.com
Doyle Munroe Consultants, Inc.		UUCP: ...uunet!thehulk!munroe
267 Cox St.				Office: (508) 568-1618
Hudson, Ma. 01749 USA			FAX: (508) 562-1133

GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.