[mercury-users] Mercury runtime problem on Windows

Paul Bone pbone at csse.unimelb.edu.au
Thu Aug 13 14:12:08 AEST 2009

On Thu, Aug 13, 2009 at 01:15:34PM +1000, Michael Day wrote:
> Hi,
> We're getting occasional instances of the following error from the  
> Mercury runtime on Windows 2003:
> "cannot set SIGSEGV handler: Invalid argument
> Mercury runtime: "
> It doesn't always happen though. This is in a situation where many  
> instances of the same Mercury process are being invoked concurrently.
> Could there be some kind of conflict between processes causing this?
> We've seen a similar error before on other versions of Windows if I  
> recall correctly, but in that case it was repeatable and not transient.

This should not happen, each process should have it's own set of handlers
independant of any other process.  I think this would be an implementation
problem in Windows.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 489 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/users/attachments/20090813/76aa0ebb/attachment.sig>

More information about the users mailing list