[m-dev.] Mercury compiler bug symptom

[Julien Fischer]

On Sat, 6 Oct 2007, Ralph Becket wrote:

> I've made a change to pretty_printer.m in a workspace and tried testing
> it on a g12 workspace:
>
> saturn:~/g12-lp/g12/solvers/mcplex/new_tests $ which mmc
> /home/mercury/rafe/mercury/ws-lib/mercury/bin/mmc
> saturn:~/g12-lp/g12/solvers/mcplex/new_tests $ mmc --make opl146 --grade asm_fast.gc.tr.debug
> Making Mercury/int3s/opl146.int3
> Making Mercury/int3s/cvector.int3
> Making Mercury/ints/cvector.int
> Making Mercury/ints/opl146.int
> Making
> Mercury/asm_fast.gc.tr.debug/x86_64-unknown-linux-gnu/Mercury/cs/cvector.c
>
> *** Mercury runtime: caught segmentation violation ***
> cause: address not mapped to object
> address involved: 0x1
> This may have been caused by a stack overflow, due to unbounded
> recursion.
> exiting from signal handler
> ** Error making
> `Mercury/asm_fast.gc.tr.debug/x86_64-unknown-linux-gnu/Mercury/cs/cvector.c'.
>
> I've seen this once before; does anyone know what might cause this?
> (I'm assuming it's not stack overflow due to my change to
> pretty_printer.m.)

Does the same thing occur in non .debug grades?

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