File-Format-Errors.html 4.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. <html lang="en">
  2. <head>
  3. <title>File Format Errors - avram - a virtual machine code interpreter</title>
  4. <meta http-equiv="Content-Type" content="text/html">
  5. <meta name="description" content="avram - a virtual machine code interpreter">
  6. <meta name="generator" content="makeinfo 4.13">
  7. <link title="Top" rel="start" href="index.html#Top">
  8. <link rel="up" href="Diagnostics.html#Diagnostics" title="Diagnostics">
  9. <link rel="prev" href="Overflow-Errors.html#Overflow-Errors" title="Overflow Errors">
  10. <link rel="next" href="Application-Programming-Errors.html#Application-Programming-Errors" title="Application Programming Errors">
  11. <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
  12. <meta http-equiv="Content-Style-Type" content="text/css">
  13. <style type="text/css"><!--
  14. pre.display { font-family:inherit }
  15. pre.format { font-family:inherit }
  16. pre.smalldisplay { font-family:inherit; font-size:smaller }
  17. pre.smallformat { font-family:inherit; font-size:smaller }
  18. pre.smallexample { font-size:smaller }
  19. pre.smalllisp { font-size:smaller }
  20. span.sc { font-variant:small-caps }
  21. span.roman { font-family:serif; font-weight:normal; }
  22. span.sansserif { font-family:sans-serif; font-weight:normal; }
  23. --></style>
  24. </head>
  25. <body>
  26. <div class="node">
  27. <a name="File-Format-Errors"></a>
  28. <p>
  29. Next:&nbsp;<a rel="next" accesskey="n" href="Application-Programming-Errors.html#Application-Programming-Errors">Application Programming Errors</a>,
  30. Previous:&nbsp;<a rel="previous" accesskey="p" href="Overflow-Errors.html#Overflow-Errors">Overflow Errors</a>,
  31. Up:&nbsp;<a rel="up" accesskey="u" href="Diagnostics.html#Diagnostics">Diagnostics</a>
  32. <hr>
  33. </div>
  34. <h4 class="subsection">1.6.4 File Format Errors</h4>
  35. <p>Certain application crashes result from an application not adhering
  36. to the required conventions about data and file formats, or because the
  37. application was invoked in the wrong mode (<a href="Modes-of-Operation.html#Modes-of-Operation">Modes of Operation</a>). These
  38. are the following.
  39. <dl>
  40. <dt><var>application-name</var><code>: invalid text format (code </code><var>nn</var><code>)</code><dd><a name="index-g_t_0040code_007binvalid-text-format_007d-77"></a>An application that was expected to return a string of characters to
  41. be written to a text file returned data that did not correspond to any
  42. valid character representation.
  43. <br><dt><var>application-name</var><code>: null character in prompt</code><dd>An interactive application (invoked rightly or wrongly with <samp><span class="option">-i</span></samp>,
  44. <samp><span class="option">-t</span></samp>, or <samp><span class="option">-s</span></samp>) is required to exchange strings of non-null
  45. characters internally with <code>avram</code>, and used a null.
  46. <br><dt><var>application-name</var><code>: invalid file name (code </code><var>nn</var><code>)</code><dd>The data structure representing a file obtained from an application
  47. has a name consisting of something other than character strings. This
  48. error could be the result of a filter mode application (<a href="Filter-Mode.html#Filter-Mode">Filter Mode</a>) being invoked in parameter mode.
  49. (<a href="Parameter-Mode.html#Parameter-Mode">Parameter Mode</a>)
  50. <br><dt><var>application-name</var><code>: null character in file name</code><dd><a name="index-g_t_0040code_007bnull-character-in-file-name_007d-78"></a>Similar to the above errors.
  51. <br><dt><var>application-name</var><code>: bad character in file name</code><dd><a name="index-g_t_0040code_007bbad-character-in-file-name_007d-79"></a>Slashes, backslashes, and unprintable characters other than spaces are
  52. also prohibited in file names.
  53. <br><dt><var>application-name</var><code>: invalid output preamble format</code><dd><a name="index-g_t_0040code_007binvalid-output-preamble-format_007d-80"></a>According the format used by <code>avram</code> for data files, a data file
  54. may contain an optional text portion, known as the preamble. This
  55. error occurs when a data file obtained from an application can not be
  56. written because the preamble is something other than a list of
  57. character strings.
  58. <br><dt><var>application-name</var><code>: invalid file specification</code><dd><a name="index-g_t_0040code_007binvalid-file-specification_007d-81"></a>This error occurs in situations where the data structure for a file
  59. obtained by evaluating the application is too broken to permit any
  60. more specific diagnosis.
  61. <br><dt><code>avram: invalid raw file format in </code><var>application-name</var><dd><a name="index-g_t_0040code_007binvalid-raw-file-format_007d-82"></a>The file containing the virtual machine code was not able to be
  62. loaded, because the code was not in a recognizable format. Either the
  63. file has become corrupted, the compiler that generated it has a
  64. bug in it, or the wrong file was used as a virtual code file.
  65. </dl>
  66. </body></html>