Even more interesting...

[Stephen Weeks]

> But I have another idea:
...
> Whenever I get the 487 error code - I could just ignore it

I don't think this is such a good idea either.  Here are two more
possibilities.

* Never shrink the stack or heap.
  It should be easy to modify gc.c to do this.  The weird smunmap
  calls only happen when shrinking memory regions. 

* Fix gc.c to not use weird smunmap calls.
  While not as easy as the above, this shouldn't be too bad.
  Whenver the GC uses the smunmap call to shrink a chunk of memory
  (either a stack or heap), you could instead allocate a new chunk of
  memory of the smaller size, copy over, and free the old memory.  Or,
  you could try using realloc, as Henry mentioned.