🚀 go-pugleaf

I have gcc 1.40 installed for our SPARCs under SunOS 4.1.1 and have started
seeing some strange behavior while using DbxTool.  We recently switch most
of our machines to SPARCs, so I suspect it is related to this, since we
never saw the problem with the Sun3 machines.

The problem seems to be related to DbxTool reading the symbol table information
and getting confused.  If the code is compiled under the Sun cc, DbxTool is
able to interpret a variables type with no problems (it knows whether a
variable is an array, struct, etc.).  If the same code is compiled under gcc
and then debugged under DbxTool, the interpretation of some variables is
completely wrong.  In one case the print command produced a struc listing
for a variable declared as char **.  The struct listing had several members
and looked real nice, but it sure was not what the variable was meant to be.

Since this happens in a rather unpredictable way, I don't have any nice clear
small examples to pass along.  I have not checked to see if any other
debuggers (gdb, Saber-C) have similar problems.

I have read this group for a few weeks to see if anyone else noticed this,
but have seen nothing, so I decided to post this request for help.
--
Alan Bair                 SSDT Logic Synthesis,
Motorola, Inc.            Simulation & Test
Austin, Texas             abair@ssdt-oakhill.sps.mot.com