Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utah-cs.UUCP
Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!zehntel!hplabs!hao!seismo!utah-cs!brownc
From: brownc@utah-cs.UUCP (Eric C. Brown)
Newsgroups: net.micro.pc
Subject: DEBUG bugs...
Message-ID: <2984@utah-cs.UUCP>
Date: Fri, 3-Aug-84 12:53:22 EDT
Article-I.D.: utah-cs.2984
Posted: Fri Aug  3 12:53:22 1984
Date-Received: Sun, 5-Aug-84 05:34:19 EDT
Organization: Univ of Utah CS Dept
Lines: 23

I was attempting to bring up Kermit V. 2.26 on a Zenith Z-100 when I found 
a truly wonderful bug.  DEBUG (at least the 2.0 version) breaks the Kermit
command processor.   When Kermit is run without the debugger, the command
processor works fine.  When Kermit is run under DEBUG, the command processor
will no longer accept commands.  All it will do is print 

?Illegal command

and nothing else.   I believe that what is happening is that the code 
around cmky2x is being trashed (discovered by tracing through the command
processor). 

So.   Does anyone have a working version of DEBUG, and if not, does anybody
know of a debugger that will debug Kermit??

Thanks,
	Eric C. Brown

	brownc@utah-cs

	..!harpo!utah-cs!brownc

Hacking.. It's not just a job, it's an obsession.