[mercury-users] Mercury runtime problem on Windows

Julien Fischer juliensf at csse.unimelb.edu.au
Thu Aug 13 23:43:35 AEST 2009

Hi Michael,

On Thu, 13 Aug 2009, Michael Day wrote:

>> AIUI this is for the detection and slightly-more-graceful handling of 
>> memory
>> access errors.  In some places in the runtime we use mprotect() to ensure 
>> that
>> reads or writes to that memory are caught as errors, I forget exactly what 
>> this
>> is for but perhaps to catch stack overruns, this may be related to our 
>> handler.
> In this case it seems that the signal handler is only necessary to give a 
> suitable error message for runtime or program errors. Since in this case it 
> is actually causing a serious error, and is not required for correct program 
> operation, it would be nice if it were optional.
> Can this be done? It seems to be simply a matter of ignoring the return 
> value, or perhaps printing a message or aborting only in debug grades?

Is your program an executable generated by the Mercury compiler, or are
the Mercury bits compiled into a library that is used by something else?

mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au

More information about the users mailing list