RE: [Caml-list] Segmentation fault from Array.append

[Lin Hong <lhong@amnh.org>]

if by "c stubs" you mean some function that holding up place but does nothing, we are not doing any of that.

and yes it's reproducible on one mac, I will test it on other machine with Ocaml4.X.X


Thanks,
Lin Hong
American Museum of Natural History
POY website :
https://code.google.com/p/poy/
http://research.amnh.org/scicomp/scripts/download.php

________________________________________
From: David House [dhouse@janestreet.com]
Sent: Tuesday, October 16, 2012 11:10 AM
To: Lin Hong
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Segmentation fault from Array.append

Segfaults in the GC are often the fault of random heap corruption. Are
you using any C stubs that might be at fault here?

Is the fault reproducable?

On Tue, Oct 16, 2012 at 4:08 PM, Lin Hong <lhong@amnh.org> wrote:
> Hi, all
>
> we got a Segmentation fault with Ocaml 4.0.0 and 4.0.1 from append function
> of Array. gdb traceback give us this:
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x0000000107b65000
> 0x0000000100488840 in mark_slice ()
> (gdb) backtrace
> #0  0x0000000100488840 in mark_slice ()
> #1  0x0000000100489216 in caml_major_collection_slice ()
> #2  0x000000010048984c in caml_check_urgent_gc ()
> #3  0x000000010048f26d in caml_array_gather ()
> #4  0x000000010048f42e in caml_array_append ()
> #5  0x00000001003ef216 in .L363 ()
> Previous frame inner to this frame (gdb could not unwind past this frame)
> (gdb)
>
> looks like the error is from array.c
>
> we don't see this problem with Ocaml3.X.X, they have different array
> function in the cside anyway.
>
> Does anyone else have similar problem like this?
>
>
> Thanks in advance for any suggestions.
>
> Cheers,
> Lin Hong
> American Museum of Natural History
> POY website :
> https://code.google.com/p/poy/
> http://research.amnh.org/scicomp/scripts/download.php