[mercury-users] Segfaults and stack overflows?

[Peter Hawkins]

Hi...

Can anyone suggest ways of tracking down the cause of the following segfault? 
(a stack overflow is quite possible, but how does one know _which_ stack 
should be made bigger? I tried tweaking everything I could see in 
MERCURY_OPTIONS). The relevant system has plenty of memory available.

Output:
Steiner system S(5,7,28)
Propagation method: domain
Number of blocks: 4680

*** Mercury runtime: caught segmentation violation ***
PC at signal: 134655154 (806acb2)
address involved: 0x2
This may have been caused by a stack overflow, due to unbounded recursion.

Thanks,
Peter
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------