diff6-10.chapter10.txtこのページは最後に更新されてから1年以上経過しています。情報が古い可能性がありますので、ご注意ください。 last mod. 2008-08-28 (木) 09:52:13
40,44c40,43 < Under several versions of Windows, bytecode executable files < are self-executable only if their name ends in .exe. It is < recommended to always give .exe names to bytecode executables, < e.g. compile with ocamlc -o myprog.exe ... rather than ocamlc -o < myprog .... --- > Under several versions of Windows, bytecode executable files are > self-executable only if their name ends in .exe. It is recommended to always > give .exe names to bytecode executables, e.g. compile with ocamlc -o > myprog.exe ... rather than ocamlc -o myprog .... 54a54 > 56c56 < ``back trace'' of the execution, showing where the exception was raised and --- > "back trace" of the execution, showing where the exception was raised and 66a67 > -version Print version and exit. 83,86c84,87 < parameter specification is an option letter followed by an = sign, a < decimal number, and an optional multiplier. There are nine options, six of < which correspond to the fields of the control record documented in section < 20.10. --- > parameter specification is an option letter followed by an = sign, a decimal > number (or an hexadecimal number prefixed by 0x), and an optional > multiplier. There are nine options, six of which correspond to the fields of > the control record documented in section 20.10. 91,95c92,96 < parsers. When this option is on, the pushdown automaton that executes < the parsers prints a trace of its actions. This option takes no < argument. < s (minor_heap_size) Size of the minor heap. < i (major_heap_increment) Minimum size increment for the major heap. --- > parsers. When this option is on, the pushdown automaton that executes the > parsers prints a trace of its actions. This option takes no argument. > s (minor_heap_size) Size of the minor heap. (in words) > i (major_heap_increment) Default size increment for the major heap. (in > words) 101,110c102,111 < 1 (= 0b0000000001) Start of major GC cycle. < 2 (= 0b0000000010) Minor collection and major GC slice. < 4 (= 0b0000000100) Growing and shrinking of the heap. < 8 (= 0b0000001000) Resizing of stacks and memory manager tables. < 16 (= 0b0000010000) Heap compaction. < 32 (= 0b0000100000) Change of GC parameters. < 64 (= 0b0001000000) Computation of major GC slice size. < 128 (= 0b0010000000) Calling of finalization functions < 256 (= 0b0100000000) Startup messages (loading the bytecode executable < file, resolving shared libraries). --- > 1 (= 0x001) Start of major GC cycle. > 2 (= 0x002) Minor collection and major GC slice. > 4 (= 0x004) Growing and shrinking of the heap. > 8 (= 0x008) Resizing of stacks and memory manager tables. > 16 (= 0x010) Heap compaction. > 32 (= 0x020) Change of GC parameters. > 64 (= 0x040) Computation of major GC slice size. > 128 (= 0x080) Calling of finalisation functions > 256 (= 0x100) Startup messages (loading the bytecode executable file, > resolving shared libraries). 117c118 < export OCAMLRUNPARAM='b,s=256k,v=1' --- > export OCAMLRUNPARAM='b,s=256k,v=0x015' 119,121c120,127 < tells a subsequent ocamlrun to print backtraces for uncaught exceptions, < set its initial minor heap size to 1 megabyte and print a message at the < start of each major GC cycle. --- > tells a subsequent ocamlrun to print backtraces for uncaught exceptions, set > its initial minor heap size to 1 megabyte and print a message at the start > of each major GC cycle, when the heap size changes, and when compaction is > triggered. > > CAMLRUNPARAM If OCAMLRUNPARAM is not found in the environment, then > CAMLRUNPARAM will be used instead. If CAMLRUNPARAM is not found, then the > default values will be used. 167a174 > 186c193 < Uncaught exception The program being executed contains a ``stray'' exception. --- > Uncaught exception The program being executed contains a "stray" exception. 199c206 < your machine provides. In other cases, the ``out of memory'' message reveals --- > your machine provides. In other cases, the "out of memory" message reveals 205,211c212,217 < displays lots of ``Growing stack...'' messages, this is probably a looping < recursive function. If it displays lots of ``Growing heap...'' messages, < with the heap size growing slowly, this is probably an attempt to construct < a data structure with too many (infinitely many?) cells. If it displays few < ``Growing heap...'' messages, but with a huge increment in the heap size, < this is probably an attempt to build an excessively large array or string. < --- > displays lots of "Growing stack..." messages, this is probably a looping > recursive function. If it displays lots of "Growing heap..." messages, with > the heap size growing slowly, this is probably an attempt to construct a > data structure with too many (infinitely many?) cells. If it displays few > "Growing heap..." messages, but with a huge increment in the heap size, this > is probably an attempt to build an excessively large array or string. |