[m-rev.] for review: call MR_fatal_abort when handling strange seg faults
Zoltan Somogyi
zs at cs.mu.OZ.AU
Thu Mar 16 12:58:56 AEDT 2006
On 16-Mar-2006, Ian MacLarty <maclarty at cs.mu.OZ.AU> wrote:
> runtime/mercury_memory_handlers.c:
> Instead of just aborting when a "strange" segfault or bus error is
> caught, call MR_fatal_abort which will print a stack dump and display
> the last trace event in debugging grades. Call MR_fatal_abort
> instead of MR_fatal_error because the comment above MR_fatal_abort says
> it is safe to call from signal handlers.
That should be fine.
Zoltan.
--------------------------------------------------------------------------
mercury-reviews mailing list
post: mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------
More information about the reviews
mailing list