When analyzing external types, CAESAR.ADT 4.5 may issue the following error message:
-- caesar.adt 4.5 -- H. Garavel, R. Mateescu, M. Sighireanu & Ph. Turlier -- caesar.adt: syntax analysis of ``rcc'' caesar.adt: semantic analysis of ``rcc'' caesar.adt: - gates binding caesar.adt: - processes binding caesar.adt: - types binding caesar.adt: - signature analysis caesar.adt: - sorts binding caesar.adt: - variables binding caesar.adt: - operations binding caesar.adt: - functionality analysis caesar.adt: interface of ``rcc'' caesar.adt: verification of ``rcc'' caesar.adt: compilation of ``rcc'' caesar.adt: external type survey of ``rcc'' #005 bug : unavailable option in this software caesar.adt: optimization of ``rcc'' caesar.adt: C translation of ``rcc'' caesar.adt: indentation of ``rcc''SOLUTION:
This error message is meaningless and can be safely ignored. Even if this message is displayed, CAESAR.ADT works correctly.
Clicking on a ".aut" file and choosing "Execute/Standard simulation" does not work properly because an intermediate BCG file is erased too early.
SOLUTION:Edit file $CADP/src/eucalyptus/eucalyptus.tcl and remove the following line:
Execute "rm -f $Tmp_File"in the definition of "proc Open_Caesar".
The exp.open tool in the $CADP/com directory does not have the correct access rights, in particular, it is not executable, and this causes an error when run from the Eucalyptus graphical interface.
SOLUTION:Type the following Unix command:
chmod a+rx $CADP/com/exp.open
If the environment variable $CADP_CC is set to "gcc", the BCG_IO tool (sometimes) does not work properly and stops after issuing the following message:
bcg_io: wrong number of parameters bcg_dynamic: dynamic program errorSOLUTION:
This is a known problem in the BCG library, which will be fixed in the next
CADP release. In the meantime, the solution is to use the SunSoft C compiler
(located in "/opt/SUNswpro/bin"), for which BCG_IO works properly, instead
of "gcc".
Alternately, upon request to Hubert.Garavel@inria.fr, we can provide an updated version of the BCG library that will solve the problem.
If the environment variable $CADP_CC is set to "gcc", the BCG_DRAW tool (sometimes) stops silently: the Ghostview window is not created. Instead a "core" file is created in the current directory. As a consequence, the BCG_EDIT tool does not work properly.
SOLUTION:
This is a known problem in the BCG library, which will be fixed in the next
CADP release. In the meantime, the solution is to use the SunSoft C compiler
(located in "/opt/SUNswpro/bin"), for which BCG_DRAW and BCG_EDIT work
properly, instead of "gcc".
Alternately, upon request to Hubert.Garavel@inria.fr, we can provide an updated version of the BCG library that will solve the problem.
If the environment variable $CADP_CC is set to "gcc", the ALDEBARAN tool (sometimes) makes a core dump when applied to BCG files.
SOLUTION:
This is a known problem in the BCG library, which will be fixed in the next
CADP release. In the meantime, the solution is to use the SunSoft C compiler
(located in "/opt/SUNswpro/bin"), for which BCG_DRAW and BCG_EDIT work
properly, instead of "gcc". Also, this problem can be avoided by using
".aut" files instead of ".bcg" files.
Alternately, upon request to Hubert.Garavel@inria.fr, we can provide an updated version of the BCG library that will solve the problem.
If the Aldebaran format or the Graph format is selected for LTS generation (instead of the BCG format), this selection remained later when the OPEN/CAESAR tools were invoked, causing disturbances.
SOLUTION:This problem does not occur if the BCG format is used.
If you have selected the ALDEBARAN format and want to use the OPEN/CAESAR tools later, exit the EUCALYPTUS Graphical User-Interface and re-enter it again.
Alternately, upon request to Hubert.Garavel@inria.fr, we can provide an updated version of the "eucalyptus.tcl" file that will solve the problem.