<incomplete type> problems with gdb 4.16

[Bob Sidebotham <rns at fore dot com>]

Gdb has become virtually unusable with egcs-1.0 for C++ programs
because it frequently complains that types are "incomplete". Does
anyone have any information on this?

For example:

	(gdb) p expected
	$4 = <incomplete type>
	(gdb) bt
	#0  tokenlist::next (this=<incomplete type>, expected=<incomplete type>)
	    at linux/obj/tools/smfgen/token.cc:133
	#1  0x804d34e in main (argc=2, argv=0xbffffa8c)
	    at linux/obj/tools/smfgen/main.cc:69
	(gdb) 

Here, "this" is the object pointer, and "expected" is simply a const char *.

This happens with egcs-1.0 on both SunOS and RedHat Linux platforms,
with gdb 4.16 on linux and gdb 4.15 on SunOS.

Thanks,
Bob Sidebotham
rns@fore.com