🚀 go-pugleaf

In article <DARREN.93Feb2190200@tuba.geo.ucalgary.ca> darren@geo.ucalgary.ca (Darren Foltinek) writes:
>Since installing the 2.3.3 version of gcc, I have not been able to run 
>debuggers on most of the programs I've compiled with gcc.
>
>Both the UPS debugger (plug: A GREAT debugger) and xdbxtool (dbx) fail.

Thanks for the backhanded plug for ups :-)

>UPS fails with the following error whenever I attempt to print a variable:
>
>Fatal interal error: bad name in parse_name (aborting) ...
>Dumping core ... IOT trap (core dumped)

This is due to gcc emitting symbol table entries for certain enum declarations
that contain either empty names or names with white space characters at the
start.  I have added a workaround for this in ups.  You can get the patch
by anonymous FTP from unix.hensa.ac.uk.  The patch file path is:

	/misc/unix/ups/ups-2.45-to-2.45.2.patch

There is also a compressed tar file containing the complete 2.45.2 release -
ups-2.45.2.tar.Z in the same directory.  The gcc workaround is the only
difference between releases 2.45 and 2.45.2 of ups.

>And dbx displays bogus values of variables, even right after they've 
>been assigned.

This doesn't sound like the same problem to me, although I know nothing
about the internals of dbx.

Mark