🚀 go-pugleaf

Environment: 4.2bsd on a VAX.

I had adb coredump on me!  It seems to be repeatable (this is of course
not how it happened the first time):

	% adb
	00008000=f
	Floating exception (core dumped)
	%

It's pretty obvious to anyone who knows VAX floating-point format what
is going wrong.  That value is a floating reserved operand.  But the
last thing adb should do is coredump over it (or over anything for that
matter)!  I expect a message; perhaps something like "(reserved
operand)" instead of the floating-point value.

I also had lex coredump on me.  I had a file `x' and a file `x.lex'; by
mistake I said `lex x' rather than `lex x.lex'.  Lex coredumped!
Again, I would expect error messages (lots of them).  Here it is, done
deliberately:

	% lex << FOO
	/* note that // gets turned into /* and */ by comcon
	/**/
	
	int variable;		// comment
	FOO
	Segmentation fault (core dumped)
	%

Unfortunately /usr/bin/lex is stripped so I have no idea where it is
dying.

Oh well.  Perhaps someday I will even have fixes for these (not this
time though).
-- 
					der Mouse

USA: {ihnp4,decvax,akgua,utzoo,etc}!utcsri!mcgill-vision!mouse
     philabs!micomvax!musocs!mcgill-vision!mouse
Europe: mcvax!decvax!utcsri!mcgill-vision!mouse
        mcvax!seismo!cmcl2!philabs!micomvax!musocs!mcgill-vision!mouse
ARPAnet: utcsri!mcgill-vision!mouse@uw-beaver.arpa

Wizard:  One who can find and fix bugs in an emergency
	(such as during re-entry).