lotus



previous page: C11.3.2) Errors when evaluating expressions involving reals and external calls
  
page up: BETA Programming Language FAQ
  
next page: C13) Problem with floating point expressions in connection with repetitions

C12) Tracing the work of compiler?




Description

This article is from the FAQ, by with numerous contributions by others.

C12) Tracing the work of compiler?

In the extremely rare event that the compiler crashes during compilation of
your program, you may yourself do some tracing of the compilation to find
out what particular part of your program, that makes the compiler crash. You
do this by specifying some compiler switches:

1. If the compiler crashes during *code generation* of a fragment, please
do this:

beta -s 308 311 0 <file>

This will make the compiler print out each declaration and imperative
just before code is generated for it. Thus when the compiler crashes,
you can see what part of your program caused it.
2. If the compiler crashes during *checking* of a fragment, please do
this:

beta -s 191 192 193 0 <file>

This will make the compiler print out each descriptor, declaration and
imperative just before checking it. Thus when the compiler crashes, you
can see what part of your program caused it.

In version v5.1 of the compiler, you can use the two new compiler switches
--traceCode and --traceCheck instead.

 

Continue to:















TOP
previous page: C11.3.2) Errors when evaluating expressions involving reals and external calls
  
page up: BETA Programming Language FAQ
  
next page: C13) Problem with floating point expressions in connection with repetitions