1.6.4 File Format Errors

Certain application crashes result from an application not adhering to the required conventions about data and file formats, or because the application was invoked in the wrong mode (Modes of Operation). These are the following.

application-name: invalid text format (code nn)

An application that was expected to return a string of characters to be written to a text file returned data that did not correspond to any valid character representation.

application-name: null character in prompt

An interactive application (invoked rightly or wrongly with ‘-i’, ‘-t’, or ‘-s’) is required to exchange strings of non-null characters internally with avram, and used a null.

application-name: invalid file name (code nn)

The data structure representing a file obtained from an application has a name consisting of something other than character strings. This error could be the result of a filter mode application (Filter Mode) being invoked in parameter mode.
(Parameter Mode)

application-name: null character in file name

Similar to the above errors.

application-name: bad character in file name

Slashes, backslashes, and unprintable characters other than spaces are also prohibited in file names.

application-name: invalid output preamble format

According the format used by avram for data files, a data file may contain an optional text portion, known as the preamble. This error occurs when a data file obtained from an application can not be written because the preamble is something other than a list of character strings.

application-name: invalid file specification

This error occurs in situations where the data structure for a file obtained by evaluating the application is too broken to permit any more specific diagnosis.

avram: invalid raw file format in application-name

The file containing the virtual machine code was not able to be loaded, because the code was not in a recognizable format. Either the file has become corrupted, the compiler that generated it has a bug in it, or the wrong file was used as a virtual code file.

This document was generated on December 10, 2012 using texi2html 1.82.