[mercury-users] Debug prints get optimized away

[Michael Day]

> Note that my program was checked and delivered all the expected data on
> a smaller sample. The memory was also (most probably) not exhausted, as
> the machine has 10GB of RAM and as I already succeeded with this
> particular run before, using 0.12.2+asm_fast.gc (compiled 32bit run
> emulated on this 64bit machine) and not the current rots+hlc.gc.par,
> compiled 64bit.

If I recall correctly, hlc.gc grades crash with a segfault when you
overflow the stack, eg. by doing list operations on an enormous list or
recursing too far. This is less informative than asm_fast.gc, which prints
a detstack overflow message when this happens.

Cheers,

Michael

-- 
Print XML with Prince!
http://www.princexml.com
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------