It *looks* like a run-of-the-mill memory-badness kind of error, but
it's impossible to say without more information.
Are you able to run this through valgrind or some other memory-
checking debugger? It looks like the single process case may be the
simplest to check...?
On Aug 13, 2007,
I tried to run a code that I have running for a while now this morning,
but for some reason it is causing segmentation faults. I can't really
think of anything that I have done recently that would be causing these
errors. Does anyone have any idea?
I get this running it on more than one processo
