🚀 go-pugleaf

if you have a construct like

	switch (...)
	case ...:
	{
		static const struct {
			char *name;
			int foo;
		} predefs[] = {
		....
		};

gcc will generate an N_FUN stab entry for predefs, causing gdb to
(rightly) have fits (unmatched left brace). Is there any pressing
reason why you cannot use N_STSYM? Looking at the documentation I have
from Sun does not preclude the use of STSYM for static variables in
the text segment, whereas N_FUN has all sorts of nasty implications
one doesn't want in this case. The comment in dbxout.c:

		/* This is not quite right, but it's the closest
		   of all the codes that Unix defines.  */

is correct in saying it's not quite right...

a