stack dumps.

[Fergus Henderson]

On 19-Feb-1998, Tyson Dowd <trd at stimpy.cs.mu.oz.au> wrote:
> I have what appears to be a working version of stack dumps (for the
> det stack, anyway).
> 
> I'm now considering where to add them to the library or runtime.
> At the moment, a reasonable place to put it is in require.m, so that
> (if possible) error/1 can give a stack dump. Any other ideas?

If the implementation is C code, not Mercury code, then the runtime
directory is probably a better place.

Also if the code might need to be called from the runtime (as indeed
it might -- on stack overflow), then it will be easier if it is
part of the runtime.  (Calls in the reverse direction need to be
via a pointer, to avoid circular dependencies between the libraries.)

-- 
Fergus Henderson <fjh at cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3         |     -- the last words of T. S. Garp.