Application cache: object_cache, release, debug

Object_cache

Object_cache is a native code obtained by AOT compilation.

Object_cache is created if it is absent. More specifically, it happens:

• when you deploy an application for the first time;
• when you run the application via LyciaDesktop or LyciaWeb;
• when you perform this command in the command line - qrun --aot.

Object_cache is recreated:

• when you have changed one or more of the source files (object_cache for the changed files is recreated);
• when code generator is changed;
• when you tell Lycia compiler to build the other type of object_cache (e.g., when you have the release cache already and then build debug cache).

Object_cache is saved here:

Object_cache includes (in particular) the application's metadata (<app_name>.exe.dll) and ID files (<app_name>.exe.id); object file; PIC, BC, RELOC, DAT files (depending on the type of the object_cache), etc.

Among other things, object_cache includes this information:

• Lycia build used when building object_cache,
• code generator version used when building object_cache,
• Lycia build used when compiling the application,
• code generator version used when compiling the application,
• vendor and version of the linker used when building object_cache,
• version of the runtime C libraries,
• etc.

For example:

To include object_cache information to the application (= qrun) logs, you must set these environment variables and their values to inet.env:

QXDEBUG=PzVzT

LYCIA_SEVERITY=TRACE

QX_TRACE=1

QX_TRACE_ARG_DUMP=1

When object_cache is built, qrun checks the code generator version used to the compile the program.

If the program was compiled with the same version of the code generator that is used when building object_cache, object_cache is created.

If versions of the code generator are different, object_cache is not created, and the application crashes with this error - 9260: Module was built with the different code generator version. The error is written to the to LyciaStudio / Lycia VS Code Extension console and/or LyciaConsole and/or application logs - depending on how you obtain the output of qrun stdout.

 

Release and debug cache

There are two types of object_cache generated by Lycia compiler - release cache and debug cache.

Release cache is the object_cache optimized for maximum runtime performance.

Debug cache (also called UNL cache) is the object_cache optimized for debugging purpose.

 

Differences between release and debug cache are these:

• release cache doesn't include line info or debug info but building release cache involves a number of important optimization operations,
• debug cache includes line info and debug info but building debug cache involves no optimization.

Debug info, e.g., includes internal instructions for Lycia debugger.

 

Line info includes:

• module = name of the program,
• file = name of the source file,
• line = number of the 4gl code line where an error occurred, and
• function = name of the function where an error occurred.

Line info is displayed to the error message at runtime:

debug cache (with line info)	release cache (without line info)

Depending on the cache used - release or debug, line info can be written to error logs (= logs initialized by startlog()):

You can switch on the line info for release cache by setting the QX_REL_LINE_INFO environment variable:

QX_REL_LINE_INFO=1

 

If the cache wasn't built at deploy, it is built at the 1st run of the new application (or at the 1st run of the application after its deployed version was changed).

When you run applications from LyciaStudio, the debug cache is always used.

When you run applications via LyciaDesktop or LyciaWeb, release cache is used.

You can enable building debug cache in two ways:

• by defining the QX_UNL environment variable with in inet.env and environ.bat:

  QX_UNL=1

• by adding the --unl flag to the qrun command:

  qrun --unl

You can also set the QX_VERBOSE_CACHE environment variable in order to get verbose output for building the object_cache:

QX_VERBOSE_CACHE=1