Re: print throwing intermittent Segfaults

This is the list of stuff I usually start with when I get a problem
that doesn't seem to be tied to a particular code path.

  * code path - perhaps a particular code path is only being exercised
rarely, and it has a bug
  * forking - when child dies, all open descriptors in it's name space
also get closed
  * eval - always a good thing to look at when weird things happen
  * persistancy - globals, closures, persistant objects,
serialized/restored objects, shared memory, shared objects (between
processes)

-wjt