🚀 go-pugleaf

I have a problem with gdb-4.6 (same in 4.5) configured for m68k, COFF (don't
ask me how I got configure to work, that's another story). This uses BFD
configured for target "coff-m68k" and gdb configured to use a machine description
based on standard tm-m68k.h.

SYMPTOM:
	GDB appears to have no symbol information on .text symbols, including
filenames, and no type information on .data symbols.
	GDB has no problem reading COFF files normally when the complete tool-chain
uses COFF files.

DIAGNOSIS:
	When I dump symbols using "maintenance print symbols" there are no 
complete symbols known. Ditto for "maintenance print psymbols" for partially
read symbols. There are, however, 3797 symbols when I do "maintenance print
msymbols" for minimally-known symbols. There are also no known data types ("info
types").

	coffread.c seems to have problems with the 68k COFF format produced
by ld-2.0 (and by ld-beta-1.94). This COFF output is generated by ld-2.0 by 
translating A.OUT files produced by gas-1.92.3.

QUESTION:
	Is this what the warning that comes with BFD means by "losing symbolic
information in translation between formats"?


Andrew Smith
SynOptics Communications Inc.