D3 v9 debugging question...

[Gene Buckle]

Is there a way to get a program to break into the debugger if it hits a
"variable unassigned, zero used" error? I'm trying to track down some
annoying instances in some VERY old code.

tnx.

g.


--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.diy-cockpits.org/coll - Go Collimated or Go Home.
Some people collect things for a hobby. Geeks collect hobbies.

ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://www.scarletdme.org - Get it _today_!

Buying desktop hardware and installing a server OS doesn't make a
server-class system any more than sitting in a puddle makes you a duck.
[Cipher in a.s.r]

[Kevin Powick]

On Wednesday, 9 May 2012 10:18:29 UTC-4, geneb wrote:

Is there a way to get a program to break into the debugger if it hits a
"variable unassigned, zero used" error?  I'm trying to track down some
annoying instances in some VERY old code.

Run the program with the (e) option to break into the debugger at any non-fatal warning.

run myprog (e)

--

Kevin Powick

[Gene Buckle]

Thanks Kevin!

[Tony Gravagno]

> > geneb wrote:
> >> I'm trying to track down
> >> some annoying instances in some VERY old code.

You can also make use of the runtime-errors file in DM.

(Copy of a note I wrote into CDP) :
Just creating the file invokes the logging. Once the file is created,
you can do "list-runtime-errors" to see any errors. The dict gets
created dynamically. When you're done with diagnostics, delete the
file, or make sure you have a process to purge entries. I've seen a
couple systems where the admin forgot about the file and then wondered
why the system crawled to a halt - it was main programs trying to log
errors in a mod 1 file with a million records... Size the file
commensurate with the number of errors you expect to log.

HTH
T

[Gene Buckle]

The log file is what alerted me to the issues to begin with, but catching
them at the right time is nearly impossible without some way to make them
bugcheck when they hit the unassigned variable.

[Tony Gravagno]

> From: Gene Buckle

> The log file is what alerted me to the issues to begin with, but
catching
> them at the right time is nearly impossible without some way to make
> them bugcheck when they hit the unassigned variable.

I guess I'm not understanding the situation.
If you know where the issues are, why not do something like this? :

IF NOT(ASSIGNED(VAR)) THEN
CRT "Code error, please wait for Gene!"
CALL.TO = "gene.home":@vm:"gene.mobile"
SAY.THIS = "Error in program ":PNAME:", user ":UNAME:", port ":PORT
METHODS = "phone":@vm:"email":@vm:"sms"
CALL NOTIFY.ADMIN( METHODS, CALL.TO, SAY.THIS)
DEBUG
END

Hey, that's how I get my critical error reports these days. YMMV ;)

T

[Wjhonson]

Gene can't you wrap the program in a log file ?

The error is most likely flashing onto the screen at some point.

Then the next day, you can just scroll through the log file or do a Find for unassigned....

[Tony Gravagno]

D3 doesn't yet have COMO but an action item is on file for the enhancement. Anyone interested in this should ask TL Support to add a "me too" vote to that action item on their behalf. TL won't add features like this without adequate demand from the field.

T