LOOP
IF (1=1) THEN CONTINUE
REPEAT
END
Run this program (yes, I know - it's an endless loop).
Then Control C to break out
D is one of the debug options (and lets you know what line your on).
However, when I had something like this in my program, when it got stuck
D wasn't one of the options

The INTR.KEY entry in the VOC determines what options are given when a user
breaks out of a program. The D is for the debug option.
INTR.KEY
001 X-type - Define options available when INTR key is hit
002 ACLQD
One thing to note... The options defined in

The use of PORT.STATUS using the PID option and LAYER.STACK (PORT.STATUS
PID 123456 LAYER.STACK)
over and over again can show you what hex address in the program your process
is at. I suggest calling this
50 or 100 times in a row and inspecting the output. Once you have the hex

U2 Training and Consultancy Services
Best known as the developers of the OpenQM multivalue database, Ladybridge
Systems also provides on-site training and consultancy
services to QM and U2 sites in the UK at highly competitive prices.
We were contracted by VMark, Ardent Software, Informix and

I have to think (and I havent' yet checked) that the names of the files opened
will appear within the object code, since they have to be represented as
literal strings when they are named. Sure you could pass the name in, but then
the program wouldn't know it either, so we're just talking

Both accounts (my login and the active one) have the D in INTR.KEY
I now if I break out of a VOC, then the D is not an option
And if I break out of that same program at an input, or when it's not stuck in
a loop - the D was an option
And when I wrote the test program below - and broke out of

You mean if you break out at a BASIC input ?
If you break from a VOC you don't get the debug option, because you cannot
debug VOC entries
-Original Message-
From: George Gallen ggal...@wyanokegroup.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Wed, Oct 2, 2013 10:08

Yes...
The only time I've not had the D option, is when I break from a VOC
Which is expected, since you can't debug a VOC.
So, why would the D option not appear when you break from a basic program?
Whenit does when you break from an input
it does when another program is in a loop

The INTR.KEY in the VOC is not the only thing controlling breaking behaviour.
It specifies the maximum level of ability, not the minimum, it can be
overridden.
However, please type PTERM DISPLAY at TCL and post the results for us to review.
That is your first step, before we get more technical.

Changing the subject to not hijack the other thread. Yes, I too have a program
that basically does a strings command on the object code and either dumps all
strings or for each one looks it up in the VOC to check if it's a file.
https://github.com/ianmcgowan/PickCode/blob/master/CHECK.FILES

I Don't know? I never really looked into the PTERM signals.
I would think that is referring to a Break signal vs Control C (but I don't
know)
It's not that the Break is disabled - just the DEBUG option was missing.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org

Po-te-to/Po-ta-to.
http://technet.microsoft.com/en-us/sysinternals/bb897439.aspx
A unidata VLIST clone would be great, and I've spent a long time looking at
object code and can see some patterns, but it's grueling to get going.
-Original Message-
From:

Isn't there something that strips the symbol table during compile? If the
symbol table were suppressed the D might not appear because it couldn't do
much anyway, right?
On Oct 2, 2013 11:53 AM, George Gallen ggal...@wyanokegroup.com wrote:
I Don't know? I never really looked into the PTERM

Nothing special in the compile. Why would it give the D in one part of the
program ,
but not in another? Just very strange.
Oh wellguess I'll have to chalk it up the computer having indigestion or
something;
Hopefully it didn't pick up a virus or bug! (I think I found them all now -
but