Re: ex.err and pro
On March 27 you wrote:
>I am having trouble getting a program to run. When it stops, ex.err sho=
ws
>the values of all the variables involved, but not when they 'went bad' -=
-
>whether it was just before the program failed, or perhaps somewhat
earlier,
>after which the program kept running until it needed the bad value, whic=
h
>then threw it off the air. Without the 'when', I don't know what caused=
the
>bad value to appear.
Have you tried trace()? It can be tedious, but it shows what is going on=
=2E =
You can also stick in some print statements to show the data values. (th=
is
may not be useful for "mega-sequences") A trick I have learned is to sti=
ck
in a ? 1/0 statement which provokes a divide by zero error and a ex.err
data dump where *you* want it.
Colin Taylor
|
Not Categorized, Please Help
|
|
