caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Lin Hong <lhong@amnh.org>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] Segmentation fault from Array.append
Date: Tue, 16 Oct 2012 15:08:40 +0000	[thread overview]
Message-ID: <C960B6881E802A459A09A7DAD55690053E7C4C37@MAIL-MBX-004.internal.amnh.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 3126 bytes --]

             reply	other threads:[~2012-10-16 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 15:08 Lin Hong [this message]
2012-10-16 15:10 ` David House
2012-10-16 15:41   ` Lin Hong
2012-10-16 15:42     ` David House
2012-10-16 15:50       ` Lin Hong
2012-10-16 17:29         ` David House
2012-10-16 18:02         ` Daniel Bünzli
2012-10-16 19:08           ` Lin Hong
2012-10-17 13:33             ` Damien Doligez
2012-11-19 17:04               ` Lin Hong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C960B6881E802A459A09A7DAD55690053E7C4C37@MAIL-MBX-004.internal.amnh.org \
    --to=lhong@amnh.org \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).