Overflow-Errors.html 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263
  1. <html lang="en">
  2. <head>
  3. <title>Overflow 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="i_002fo-Errors.html#i_002fo-Errors" title="i/o Errors">
  10. <link rel="next" href="File-Format-Errors.html#File-Format-Errors" title="File Format 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="Overflow-Errors"></a>
  28. <p>
  29. Next:&nbsp;<a rel="next" accesskey="n" href="File-Format-Errors.html#File-Format-Errors">File Format Errors</a>,
  30. Previous:&nbsp;<a rel="previous" accesskey="p" href="i_002fo-Errors.html#i_002fo-Errors">i/o 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.3 Overflow Errors</h4>
  35. <p>These errors are reported by the application name prefacing one of the
  36. following messages, except as noted below.
  37. <a name="index-overflow-73"></a><a name="index-counter-overflow-74"></a><a name="index-memory-overflow-75"></a>
  38. <dl>
  39. <dt><var>application-name</var><code>: counter overflow (code </code><var>nn</var><code>)</code><dd>An overflow occurred in an unsigned long integer being used as a reference
  40. counter or something similar. This situation is very unlikely.
  41. <br><dt><var>application-name</var><code>: memory overflow (code </code><var>nn</var><code>)</code><dd>There wasn't enough memory to build an internal data structure. The
  42. most likely cause is an attempt to operate on input
  43. files that are too large. Standard remedies apply.
  44. </dl>
  45. <p>The memory overflow or counter overflow messages can also be reported
  46. without the application name preface or a code number. In these cases,
  47. they arise in the course of evaluating the function given by the
  48. application, rather than by loading the input files.
  49. <p>A counter overflow in this case is possible if the application
  50. attempts to compute the size of a very large, shared structure using
  51. native integer arithmetic.
  52. <p><a name="index-g_t_0040command_007bulimit_007d-76"></a>Memory overflows are possible due to insufficient memory for a valid
  53. purpose, but may also occur due to a non-terminating recursion in the
  54. virtual machine code. To prevent thrashing or other bad effects from
  55. runaway code, the <samp><span class="command">ulimit</span></samp> shell command is your friend.
  56. </body></html>