Silver hangs before trace can be printed for large stack overflow

[krame505]

I had been struggling with finding the reason why the ableC-prolog extension was hanging for a complex program, and just on a whim I bumped the stack space up to 700 Mb, to find that it worked perfectly. Apparently it was running out of stack space, throwing a StackOverflowError, and then trying to print a stack trace and continuing to hang or suffer more stack overflows in the process of doing so.

In the case of a stack overflow or heap exhaustion, we should probably print some sort of error message immediately before trying to generate a stack trace, as this would have saved many hours of debugging a non-existent exponential performance bug.

As a side-note, apparently some of our design practices with ableC extensions also (besides the exponential time complexity) result insane memory usage - even worse than Silver. Yay.