[mercury-users] List Append segfault

[Fergus Henderson]

On 03-Jan-2003, Michael Day <mikeday at yeslogic.com> wrote:
> 
> > Yes, that is the most likely explanation, especially if you
> > are using a system on which Mercury normally traps stack

I meant to say "... especially if you are using a system on which
Mercury normally traps seg faults and prints out an error message,
but this seg fault was not trapped."

> I remember getting detstack exceptions in the past rather than segfaults;  
> is this a difference between asm_fast.gc and hlc.par.gc?

Yes.  This is a difference between --high-level-code (hl* grades)
and --no-high-level-code.  The --high-level-code back-end uses the
system stack, which makes it hard to trap stack overflow.
The --no-high-level-code back-end uses our own Mercury stacks,
for which it is a lot easier to trap stack overflow.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-users mailing list
post:  mercury-users at cs.mu.oz.au
administrative address: owner-mercury-users at cs.mu.oz.au
unsubscribe: Address: mercury-users-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-users-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------