HP3000-L Archives

February 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tracy Pierce <[log in to unmask]>
Reply To:
Tracy Pierce <[log in to unmask]>
Date:
Fri, 16 Feb 2001 08:33:26 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (58 lines)
Re
>11. [Janet Nutsford revised by Stan Sieler] When debugging screens, such as
>VPLUS, common practice in the past was to direct stdlist to a fixed ldev
>terminal. There is no solution in a VT environment. Stan suggested being
>able to "open" an existing VT connection.

The problem AS STATED is easily circumvented - I've posted an easy
workaround to this version of the problem several times, and it appears
again below.

But the problem continues to exist, I believe, for users of an INTERACTIVE
debugger such as DEBUG/iX (or, more simply, for a programmer using both
DISPLAY and ACCEPT in her embedded debugging code), which would also require
redirection of STDIN or STDINX or (??).

Making a couple probably incorrect assumptions, a normal run defaults to
something like...
:file vpout=myscreen
:file vpin=mykeyboard
:file stdin=mykeyboard
:file stdlist=myscreen
:run myVPapp
... which can easily be allowed to take care of DISPLAYs on a separate
(unknown) device by adding...

:file DBUGOUT;NOBUF;SHR;SAVE;GMULTI;MSG
:run myVPapp;STDLIST=*DBUGOUT

...which dumps DISPLAY output into DBUGOUT, easily readable via adjacent
non-nailed device via...

:QE 67
/:FILE DBUGOUT;NOBUF;SHR;SAVE;GMULTI;MSG
/LQ *DBUGOUT

I do this "all the time" and it works great for output via DISPLAY.  But I'm
not sure how to complete the solution via redirect of the DBUGIN file, and
it seems that it might require yet another session since the DBUGIN file
displayer is already busy responding to xon xoff ctly etc while reading
DBUGOUT.

Would someone of you experienced Debug/iX users be willing to try similar
tricks for redirection of STDIN?

:FILE DBUGIN;NOBUF;SHR;SAVE;GMULTI;MSG
:FILE DBUGOUT;NOBUF;SHR;SAVE;GMULTI;MSG
:run myVPapp;STDIN=*DBUGIN;STDLIST=*DBUGLIST

...should work just fine, but do the openers of DBUGOUT and DBUGIN have to
be separate sessions?

[and for those of you dissecting the MSG file equates, no, I dunno exactly
all the details of why this particular set of FILE parms works so well; it
just does, and works on both 'ends' of the message file.  (but (d)onna, this
is an example of GMULTI is better than MULTI!)

Tracy Pierce

ATOM RSS1 RSS2