| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2069.1 | | QUARK::LIONEL | Free advice is worth every cent | Thu Jan 18 1990 09:23 | 5 |
| $ DEFINE DBG$DECW$DISPLAY " "
The space in the equivalence name is important.
Steve
|
| 2069.2 | In conjunction, the new CREATE TERMINAL command is handy ... | ARTFUL::SCOTT | Mikey hates it. | Thu Jan 18 1990 14:02 | 13 |
| In addition to the definition in .1, under VMS V5.3, I define a symbol to make
a separate DECterm for the debugger, like so:
$ DWIN*DOW ==-
"CREATE/TERMINAL/NOPROCESS"+-
"/WINDOW=(TITLE="""+NODE+"::Debugger"","+-
"ICON="""+NODE+"::Debugger"",ROWS=40)"+-
"/DEFINE=(TABLE=LNM$JOB,DBG$INPUT,DBG$OUTPUT)"
This brings us back to the same wonderful level of functionality attained with
the debugger using VWS. (The only annoyance is having to give the "DWINDOW"
command prior to each debugging session, since the window disappears as soon
as DEBUG deassigns its channel to it).
|
| 2069.3 | | VANISH::BAILEY | Fear eats the Soul | Thu Jan 18 1990 14:46 | 20 |
| >(The only annoyance is having to give the "DWINDOW"
>command prior to each debugging session, since the window disappears as soon
>as DEBUG deassigns its channel to it).
Wag..
$ Spawn/NOwait/In=nl:/out=nl: @L
where L.com contains..
$ OPEN/WRITE OUT DBG$OUTPUT
$ LOOP:
$ WAIT 20:30:00
$ GOTO LOOP
and now the DBG window reference count should never go to zero
|
| 2069.4 | Actually, you don't even need an extra process... | ARTFUL::SCOTT | Mikey hates it. | Thu Jan 18 1990 18:45 | 11 |
| RE: .3
Thanks for the suggestion--I hadn't thought of that. However, once you create
the debug window, all you have to do is something like:
$ open/share junk dbg$output
in the same process you gave the "DWINDOW" command (usually the one where I'm
invoking the program being debugged)--you don't need to spawn an extra process
just to hold onto the window. Lord knows I spend enough time waiting for VMS
to create processes, without adding unnecessary ones 8^).
|
| 2069.5 | This one's been in VMS since V1 | PRNSYS::LOMICKAJ | Jeffrey A. Lomicka | Fri Jan 19 1990 11:48 | 2 |
| Why not just $ ALLOCATE DBG$OUTPUT? That's what the command is for.
|
| 2069.6 | I'd forgotten it was there! | ARTFUL::SCOTT | Mikey hates it. | Fri Jan 19 1990 14:01 | 6 |
| RE: .-1
Thanks--for some reason, I can't remember the last time I used the ALLOCATE
command. Probably because most of my work for the past few years has been
standalone in privileged accounts either on my workstation or on some lab
system.
|
| 2069.7 | | MINNIE::DOUG | just sing it like you feel it | Thu Jan 25 1990 12:18 | 14 |
| i'm bothered by the fact that lots of people (myself included) are
using these tricks in order not to use the decwindows interface
of the debugger. at first, i thought that i must be using it
incorrectly, but everyone seems to have the same complaint.
is it possible that we are all using it incorrectly? for example, a
much better way of using it would be if allowed you to keep the
debugger running _all the time_ and had the capability to switch it
from program to program (or different runs of the same program).
similar to the way we use editors: you don't stop and start the editor
everytime you wish to edit a new program.
has the debugger this capability? if not, is it planned? is this
note in the totally wrong notesfile? :-)>
|
| 2069.8 | | QUARK::LIONEL | Free advice is worth every cent | Thu Jan 25 1990 13:25 | 8 |
| The answer to the three questions in your last paragraph are, in order:
No
It's on the wish list - I don't know about planning
Probably - TURRIS::DEBUG (or .easynote.confs.basesys.debug)
would be a better place.
Steve
|