It's my belief based on pure speculation, that the INPUT at the Debug abort
prompt is *not* the same code as the BASIC INPUT statement, and so it is not
being handled at all properly. Probably this should be reported to Rocket to
be fixed, something like when a phantom encounters a DEBUG statement kill
it ? Or something
-Original Message-
From: David A. Green dgr...@dagconsulting.com
To: 'U2 Users List' u2-users@listserver.u2ug.org
Sent: Wed, Jun 19, 2013 8:56 am
Subject: [U2] DEBUG in a Phantom issue
Has anyone seen a phantom process get stuck in a loop because of an embedded
DEBUG statement?
I would think the input at the ! prompt would have aborted the phantom, but
it just kept going saying invalid input over and over and over. just about
filled the disk.
UniData 6.1
David A. Green
(480) 813-1725
DAG Consulting
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
