Options:

Usage: pal-vm  [options] component.prc
Options:
  -v                        Verbose mode: display components loaded etc.
  -trace                    Emit trace of bytecodes executed
  -trace-after n            Emit trace of bytecodes executed, starting after n bytecodes
  -trace-exceptions         Emit trace of exceptions thrown
  -trace-exceptions-after n Emit trace of exceptions thrown, starting after n exceptions
  -trace-gc                 Emit trace of garbage collections
  -heap-size n[kM]          Set size of heap (in kbytes or Mbytes) - default is platform dependent
  -help                     Display this help
  -cp <paths>               Specify paths to search for required components
  -core <path>              Specify path for core.prc
  -constant-gc              Do a full garbage collection at every allocation

If no component path is defined then the VM takes . (the current directory)
to be the class path, but if a classpath is defined then . is not
automatically appended or prepended.

The -after options are designed to be used with a (manual) binary search
where you can generate a trace of the last few instructions before an error
occurred.

Alternatively, you can run the program once with -trace-after 0, redirecting
the output into a file with "> file.txt", then look at the bytecode numbers
with less or tail (it might be a bit big for an editor).  This can give
you an idea for a parameter for -trace-after.  In this case it is better to
use -trace-after 0 instead of -trace since the parsing of -trace takes fewer
bytecodes than the parsing of -trace-after 0 which causes confusion when
looking at bytecode counts!

The -trace-exceptions option will print a stack trace for the current coroutine
whenever an exception is thrown, whether or not it is caught (all exceptions are
caught by the basic coroutine code).  This stack trace is not as detailed as
the stack trace that can be obtained using the catchWithStackTrace: method
on Block or the stack trace methods on Java exceptions.
