Problems with Mercury

Fergus Henderson
Fri Sep 18 03:29:00 GMT 1998 wrote:
> Has anyone successfully compiled and installed Mercury lately?

Earnie Boyd <> replied:
> STATUS_ACCESS_VIOLATION relates to SIGSEGV, meaning that you've
> stepped outside the memory bounds of the program.
> 1) If the package has it's own memory allocation routines remove them
> and use the mmalloc.a library supplied by the cygwin product.
> 2) If the compilations gave you warnings concerning pointers and
> non-pointers, consider them errors and fix them.
> 3) If you pointer who has a value of NULL or zero is used as a
> reference to a memory location you will get this error.

I debugged a STATUS_ACCESS_VIOLATION problem that I encountered when
trying Mercury on cygwin32 version b19.1.  As it happens, the problem
was due to the version of gcc distributed with b19.1 generating
incorrect code, rather than any of the alternatives 1-3 above.

Stipe Tolj <> also replied:
> I had some problems too in geting the Apache HTTP Server running. Since it
> is fork()ing childs, it seems to be crashing with a STATUS_ACCESS_VIOLATION
> after trying to init a child process. I assume that this could be the
> problem at your task.

A STATUS_ACCESS_VIOLATION is a quite common diagnostic which can have
a range of different causes, and in this particular case I don't think
the problem was related to the use of fork().

As I said in my previous mail, the problems have been solved in
the lastest snapshot of the Mercury distribution and in the versions
of egcs/binutils available at Mumit Khan's site.

Fergus Henderson <>  |  "I have always known that the pursuit
WWW: < >  |  of excellence is a lethal habit"
PGP: finger fjh@        |     -- the last words of T. S. Garp.
For help on using this list (especially unsubscribing), send a message to
"" with one line of text: "help".

More information about the Cygwin mailing list