Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: VMS DEBUGGER
Message-ID: <8613@ucbvax.ARPA>
Date: Fri, 28-Jun-85 19:21:18 EDT
Article-I.D.: ucbvax.8613
Posted: Fri Jun 28 19:21:18 1985
Date-Received: Sat, 29-Jun-85 04:34:22 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 17

From: zar%xhmeia@cit-hamlet.arpa

I'd like to share a cute thing that happened to our system yesterday.
Users of my system started to complain that the DEBUGGER didn't work.
The problem showed itself as follows:
	$ FORTRAN/DEBUG prog
	$ LINK/DEBUG prog
	$ RUN prog
	%RMS-F-FNM, error in file name
	$
After a desperate search for why this was happening, I looked at the
system logical table and saw an entry for DBG$INPUT but none for
DBG$OUTPUT. Typing "ASS/SYS SYS$OUTPUT: DBG$OUTPUT" cured the problem.
Although a file name error is the reason for killing the DEBUGGER, it
seems as if a stack dump would have been better (what happens when a
user has an open statement referencing a file that doesn't exist w/no
error traps).