[m-dev.] Segmentation violations in mdb

[Ralph Becket]

> From: Adrian Pellas-Rice [mailto:apell at students.cs.mu.oz.au]
> Sent: 12 March 2001 14:47
> 
> Just out of curiousity, when mdb dies with this message, is that
> considered the fault of the program being debugged, or of mdb:
> 
> 
> *** Mercury runtime: caught segmentation violation ***
> PC at signal: 141336220 (86c9e9c)
> address involved: 0x119ae2d4
> Last trace event was event #53888.
> This may have been caused by a stack overflow, due to unbounded recursion.
> exiting from signal handler

I would imagine that this has to be considered an asynchronous exception
(i.e. could happen pretty much any time, anywhere) and is hence not covered
by the current Mercury exception scheme.  So I'd say this was not mdb's
problem.

- Ralph
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------