Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!CC5.BBN.COM!cspencer
From: cspencer@CC5.BBN.COM
Newsgroups: mod.computers.vax
Subject: Re: Debugging screen management progs
Message-ID: <8610251405.AA13147@ucbvax.Berkeley.EDU>
Date: Fri, 24-Oct-86 09:07:14 EDT
Article-I.D.: ucbvax.8610251405.AA13147
Posted: Fri Oct 24 09:07:14 1986
Date-Received: Sat, 25-Oct-86 16:11:08 EDT
References: <12249178204.18.STEINBERGER@SRI-KL.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: info-vax@sri-kl.arpa

> Have you ever tried to use the symbolic debugger to trap bugs in programs
> that make calls to the SMG$ routines?  It's not all that useful because,
> alas, the screen output is disturbed.  What I would like to do is
> have the debugger get its I/O from a different terminal than where the 
> 'screen mode' program is running.  Does anyone know how to do this?
> Are there better ways to debug 'screen mode' programs?  Thanks for the
> help.

I have had a different problem when attempting to debug
SMG$ programs. I get an error about "pasteboard already
in use" and the debugger exits. Can anyone suggest how
to sidestep this? 
						-cliff